Skip to content

DFBUGS-4290: [relesae-4.17] bundle: reinstate patch rbac on storageclient in status reporter#507

Merged
openshift-merge-bot[bot] merged 1 commit intored-hat-storage:release-4.17from
leelavg:add-rbac
Jan 7, 2026
Merged

DFBUGS-4290: [relesae-4.17] bundle: reinstate patch rbac on storageclient in status reporter#507
openshift-merge-bot[bot] merged 1 commit intored-hat-storage:release-4.17from
leelavg:add-rbac

Conversation

@leelavg
Copy link
Contributor

@leelavg leelavg commented Jan 7, 2026

4.17: status reporter patch storageclient cr
4.18: status reporter updates storageclient cr

OLM upgrades aren't atomic, during staging the upgrade OLM rolled out rbac changes which removed patch and added update even while 4.17 reporter is running.

4.17: status reporter patch storageclient cr
4.18: status reporter updates storageclient cr

OLM upgrades aren't atomic, during staging the upgrade OLM rolled out
rbac changes which removed patch and added update even while 4.17
reporter is running.

Signed-off-by: Leela Venkaiah G <lgangava@ibm.com>
@openshift-ci openshift-ci bot added the approved label Jan 7, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting labels Jan 7, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 7, 2026

@leelavg: This pull request references [Jira Issue DFBUGS-4290](https://issues.redhat.com//browse/DFBUGS-4290), 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 (odf-4.17.19) matches configured target version for branch (odf-4.17.19)
  • 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 (hnallurv@redhat.com), skipping review request.

Details

In response to this:

4.17: status reporter patch storageclient cr
4.18: status reporter updates storageclient cr

OLM upgrades aren't atomic, during staging the upgrade OLM rolled out rbac changes which removed patch and added update even while 4.17 reporter is running.

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.

@rewantsoni
Copy link
Member

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Jan 7, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leelavg, rewantsoni

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-merge-bot openshift-merge-bot bot merged commit dbe166a into red-hat-storage:release-4.17 Jan 7, 2026
9 of 10 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 7, 2026

@leelavg: [Jira Issue DFBUGS-4290](https://issues.redhat.com//browse/DFBUGS-4290): All pull requests linked via external trackers have merged:

[Jira Issue DFBUGS-4290](https://issues.redhat.com//browse/DFBUGS-4290) has been moved to the MODIFIED state.

Details

In response to this:

4.17: status reporter patch storageclient cr
4.18: status reporter updates storageclient cr

OLM upgrades aren't atomic, during staging the upgrade OLM rolled out rbac changes which removed patch and added update even while 4.17 reporter is running.

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.

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

Labels

approved jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that the 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 size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants