Skip to content

Conversation

@tmshort
Copy link
Contributor

@tmshort tmshort commented Feb 2, 2026

Ensure that the collect-profiles job is run on control-plane nodes.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 2, 2026
@openshift-ci-robot
Copy link

@tmshort: This pull request references Jira Issue OCPBUGS-74350, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Ensure that the collect-profiles job is run on control-plane nodes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from anik120 and perdasilva February 2, 2026 18:26
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 2, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tmshort

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 2, 2026
@tmshort
Copy link
Contributor Author

tmshort commented Feb 2, 2026

/jira refresh

@openshift-ci-robot
Copy link

@tmshort: This pull request references Jira Issue OCPBUGS-74350, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@tmshort
Copy link
Contributor Author

tmshort commented Feb 2, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 2, 2026
@openshift-ci-robot
Copy link

@tmshort: This pull request references Jira Issue OCPBUGS-74350, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link
Contributor

@anik120 anik120 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 2, 2026
@anik120
Copy link
Contributor

anik120 commented Feb 2, 2026

Ensure that the collect-profiles job is run on control-plane nodes.

This makes sense because olm workloads are control-plane components so ensuring these jobs are also on the same node ensures proximity.

Ensure that the collect-profiles job is run on control-plane nodes.

Signed-off-by: Todd Short <todd.short@me.com>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 2, 2026
@jianzhangbjz
Copy link
Member

/retest-required

@jianzhangbjz
Copy link
Member

Test passed. Details:

1. Build an OCP cluster with this PR 
launch 4.22,openshift/operator-framework-olm#1214 aws

jiazha-mac:~ jiazha$ oc get  clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.22.0-0-2026-02-03-021348-test-ci-ln-mvsxbhb-latest   True        False         3m16s   Cluster version is 4.22.0-0-2026-02-03-021348-test-ci-ln-mvsxbhb-latest
jiazha-mac:~ jiazha$ 

jiazha-mac:~ jiazha$ oc get nodes
NAME                          STATUS   ROLES                  AGE   VERSION
ip-10-0-108-71.ec2.internal   Ready    worker                 20m   v1.34.2
ip-10-0-116-12.ec2.internal   Ready    control-plane,master   37m   v1.34.2
ip-10-0-13-210.ec2.internal   Ready    control-plane,master   36m   v1.34.2
ip-10-0-43-222.ec2.internal   Ready    worker                 19m   v1.34.2
ip-10-0-47-180.ec2.internal   Ready    control-plane,master   36m   v1.34.2
ip-10-0-54-76.ec2.internal    Ready    worker                 27m   v1.34.2

2. Check the collect-profiles pods if running on the control-plane nodes.
jiazha-mac:~ jiazha$ oc get pods -o wide -n openshift-operator-lifecycle-manager -l app=olm-collect-profiles
NAME                              READY   STATUS      RESTARTS   AGE    IP            NODE                          NOMINATED NODE   READINESS GATES
collect-profiles-29501445-5m84v   0/1     Completed   0          31m    10.130.0.59   ip-10-0-47-180.ec2.internal   <none>           <none>
collect-profiles-29501460-48qxm   0/1     Completed   0          16m    10.129.0.77   ip-10-0-116-12.ec2.internal   <none>           <none>
collect-profiles-29501475-msjgz   0/1     Completed   0          111s   10.129.0.79   ip-10-0-116-12.ec2.internal   <none>           <none>
All of them running on the master node. LGTM.

/verified by @jianzhangbjz

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 3, 2026
@openshift-ci-robot
Copy link

@jianzhangbjz: This PR has been marked as verified by @jianzhangbjz.

Details

In response to this:

Test passed. Details:

1. Build an OCP cluster with this PR 
launch 4.22,openshift/operator-framework-olm#1214 aws

jiazha-mac:~ jiazha$ oc get  clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.22.0-0-2026-02-03-021348-test-ci-ln-mvsxbhb-latest   True        False         3m16s   Cluster version is 4.22.0-0-2026-02-03-021348-test-ci-ln-mvsxbhb-latest
jiazha-mac:~ jiazha$ 

jiazha-mac:~ jiazha$ oc get nodes
NAME                          STATUS   ROLES                  AGE   VERSION
ip-10-0-108-71.ec2.internal   Ready    worker                 20m   v1.34.2
ip-10-0-116-12.ec2.internal   Ready    control-plane,master   37m   v1.34.2
ip-10-0-13-210.ec2.internal   Ready    control-plane,master   36m   v1.34.2
ip-10-0-43-222.ec2.internal   Ready    worker                 19m   v1.34.2
ip-10-0-47-180.ec2.internal   Ready    control-plane,master   36m   v1.34.2
ip-10-0-54-76.ec2.internal    Ready    worker                 27m   v1.34.2

2. Check the collect-profiles pods if running on the control-plane nodes.
jiazha-mac:~ jiazha$ oc get pods -o wide -n openshift-operator-lifecycle-manager -l app=olm-collect-profiles
NAME                              READY   STATUS      RESTARTS   AGE    IP            NODE                          NOMINATED NODE   READINESS GATES
collect-profiles-29501445-5m84v   0/1     Completed   0          31m    10.130.0.59   ip-10-0-47-180.ec2.internal   <none>           <none>
collect-profiles-29501460-48qxm   0/1     Completed   0          16m    10.129.0.77   ip-10-0-116-12.ec2.internal   <none>           <none>
collect-profiles-29501475-msjgz   0/1     Completed   0          111s   10.129.0.79   ip-10-0-116-12.ec2.internal   <none>           <none>
All of them running on the master node. LGTM.

/verified by @jianzhangbjz

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

nodeSelector:
node-role.kubernetes.io/master: ""
tolerations:
- key: node-role.kubernetes.io/master
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: The difference is that the manifest files use 2-space indentation before the list item (-), while the script has the list item at the same indentation level as the key.

secretName: pprof-cert
restartPolicy: Never
nodeSelector:
node-role.kubernetes.io/master: ""
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we consider adding node-role.kubernetes.io/control-plane to improve forward compatibility in the future? Thanks!

jiazha-mac:~ jiazha$ oc get nodes ip-10-0-116-12.ec2.internal -o yaml | grep labels -A10|grep "node-role.kubernetes.io"
    node-role.kubernetes.io/control-plane: ""
    node-role.kubernetes.io/master: ""

@jianzhangbjz
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2026
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 64d266d and 2 for PR HEAD 5315233 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

@tmshort: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-olm 5315233 link unknown /test e2e-gcp-olm
ci/prow/e2e-gcp-ovn 5315233 link unknown /test e2e-gcp-ovn

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants