Skip to content

[release-4.21] OCPBUGS-76269: add resources to clusterOperator relatedObjects#170

Open
ankitathomas wants to merge 1 commit intoopenshift:release-4.21from
ankitathomas:relatedObjFix-4.21
Open

[release-4.21] OCPBUGS-76269: add resources to clusterOperator relatedObjects#170
ankitathomas wants to merge 1 commit intoopenshift:release-4.21from
ankitathomas:relatedObjFix-4.21

Conversation

@ankitathomas
Copy link
Contributor

track all of cluster-olm-operator's associated resources from the root-level manifests directory in relatedObjects on the olm clusterOperator.

Manual cherry-pick of #166

…jects on the olm clusterOperator

Signed-off-by: Ankita Thomas <ankithom@redhat.com>
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. 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 5, 2026
@openshift-ci-robot
Copy link

@ankitathomas: This pull request references Jira Issue OCPBUGS-76269, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-65505 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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:

track all of cluster-olm-operator's associated resources from the root-level manifests directory in relatedObjects on the olm clusterOperator.

Manual cherry-pick of #166

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 dtfranz and joelanford February 5, 2026 15:08
Copy link
Contributor

@oceanc80 oceanc80 left a comment

Choose a reason for hiding this comment

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

/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 6, 2026
@oceanc80
Copy link
Contributor

oceanc80 commented Feb 6, 2026

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ankitathomas, oceanc80

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 6, 2026
@Xia-Zhao-rh
Copy link

/retest

1 similar comment
@Xia-Zhao-rh
Copy link

/retest

@Xia-Zhao-rh
Copy link

/verified by @Xia-Zhao-rh

xzha@xzha1-mac tmp % oc get clusteroperator olm -o json| jq -c '.status.relatedObjects[]' | grep clusterroles
{"group":"rbac.authorization.k8s.io","name":"catalogd-manager-role","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"catalogd-metrics-reader","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"catalogd-proxy-role","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"operator-controller-metrics-reader","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"operator-controller-proxy-role","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"operator-controller-clusterextension-viewer-role","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"operator-controller-manager-role","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"cluster-olm-operator","resource":"clusterroles"}
xzha@xzha1-mac tmp % oc adm inspect clusteroperator/olm
Gathering data for ns/openshift-catalogd...
Gathering data for ns/openshift-operator-controller...
Gathering data for ns/openshift-cluster-olm-operator...
Wrote inspect data to inspect.local.2922270137550357011.
xzha@xzha1-mac tmp % 
xzha@xzha1-mac tmp % ls -la inspect.local.*/cluster-scoped-resources/rbac.authorization.k8s.io/clusterroles/ | grep cluster-olm-operator
-rwxr-xr-x   1 xzha  staff  5072 Feb  9 22:57 cluster-olm-operator.yaml

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

@Xia-Zhao-rh: This PR has been marked as verified by @Xia-Zhao-rh.

Details

In response to this:

/verified by @Xia-Zhao-rh

xzha@xzha1-mac tmp % oc get clusteroperator olm -o json| jq -c '.status.relatedObjects[]' | grep clusterroles
{"group":"rbac.authorization.k8s.io","name":"catalogd-manager-role","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"catalogd-metrics-reader","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"catalogd-proxy-role","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"operator-controller-metrics-reader","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"operator-controller-proxy-role","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"operator-controller-clusterextension-viewer-role","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"operator-controller-manager-role","resource":"clusterroles"}
{"group":"rbac.authorization.k8s.io","name":"cluster-olm-operator","resource":"clusterroles"}
xzha@xzha1-mac tmp % oc adm inspect clusteroperator/olm
Gathering data for ns/openshift-catalogd...
Gathering data for ns/openshift-operator-controller...
Gathering data for ns/openshift-cluster-olm-operator...
Wrote inspect data to inspect.local.2922270137550357011.
xzha@xzha1-mac tmp % 
xzha@xzha1-mac tmp % ls -la inspect.local.*/cluster-scoped-resources/rbac.authorization.k8s.io/clusterroles/ | grep cluster-olm-operator
-rwxr-xr-x   1 xzha  staff  5072 Feb  9 22:57 cluster-olm-operator.yaml

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.

@Xia-Zhao-rh
Copy link

/retest

@tmshort
Copy link
Contributor

tmshort commented Feb 12, 2026

/test lint

@jianzhangbjz
Copy link
Member

/retest-required

@jianzhangbjz
Copy link
Member

/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 13, 2026
@openshift-ci-robot
Copy link

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.z) matches configured target version for branch (4.21.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-65505 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-65505 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

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.

@openshift-ci openshift-ci bot requested a review from Xia-Zhao-rh February 13, 2026 02:45
@jianzhangbjz
Copy link
Member

/retest-required

@jianzhangbjz
Copy link
Member

/retest-required

@ankitathomas
Copy link
Contributor Author

/retest

2 similar comments
@ankitathomas
Copy link
Contributor Author

/retest

@ankitathomas
Copy link
Contributor Author

/retest

@jianzhangbjz
Copy link
Member

/retest-required

@Xia-Zhao-rh
Copy link

/retest

1 similar comment
@ankitathomas
Copy link
Contributor Author

/retest

@ankitathomas
Copy link
Contributor Author

Definitely something wrong with the lint job:
https://prow.ci.openshift.org/job-history/gs/test-platform-results/pr-logs/directory/pull-ci-openshift-cluster-olm-operator-release-4.21-lint

Runs fine locally (and in the job?), but seems to hang/get OOM killed consistently.

@tmshort
Copy link
Contributor

tmshort commented Feb 27, 2026

/test lint

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 27, 2026

@ankitathomas: The following test 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/lint 2e6dcb8 link true /test lint

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants