Skip to content

[release-4.17] OCPBUGS-63500: add missing permissions for replicasets and events #1165

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Oct 30, 2025
Merged

[release-4.17] OCPBUGS-63500: add missing permissions for replicasets and events #1165

merged 1 commit into from
Oct 30, 2025

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Oct 24, 2025

This is an automated cherry-pick of #1123

/assign opokornyy

@opokornyy
fix: add missing permissions for replicasets and events
b1dbd22 
Add permissions to insights-operator role to read
replicasets and create events in openshift-insights
namespace to resolve permission errors during
operator execution.

Signed-off-by: Ondrej Pokorny <[email protected]>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Oct 24, 2025
Merged
5 tasks
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 24, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60939 has been cloned as Jira Issue OCPBUGS-63500. Will retitle bug to link to clone.
/retitle [release-4.17] OCPBUGS-63500: add missing permissions for replicasets and events

In response to this:

This is an automated cherry-pick of #1123

/assign opokornyy

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 changed the title [release-4.17] OCPBUGS-60939: add missing permissions for replicasets and events [release-4.17] OCPBUGS-63500: add missing permissions for replicasets and events Oct 24, 2025
@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 Oct 24, 2025
@openshift-ci openshift-ci bot requested review from ncaak and tremes October 24, 2025 06:55
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 24, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-63500, 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-60939 to target a version in 4.18.0, 4.18.z, but it targets "4.21.0" 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.

In response to this:

This is an automated cherry-pick of #1123

/assign opokornyy

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.

@opokornyy
Copy link
Contributor

opokornyy commented Oct 24, 2025

/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 Oct 24, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 24, 2025

@opokornyy: This pull request references Jira Issue OCPBUGS-63500, 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.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-61972 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-61972 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

Requesting review from QA contact:
/cc @BaiyangZhou

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 BaiyangZhou October 24, 2025 06:59
@opokornyy
Copy link
Contributor

opokornyy commented Oct 24, 2025

/retest

1 similar comment
@BaiyangZhou
Copy link

BaiyangZhou commented Oct 27, 2025

/retest

@BaiyangZhou
Copy link

BaiyangZhou commented Oct 27, 2025

/test e2e-gcp-ovn-techpreview

1 similar comment
@BaiyangZhou
Copy link

BaiyangZhou commented Oct 27, 2025

/test e2e-gcp-ovn-techpreview

@openshift-ci
Copy link

openshift-ci bot commented Oct 27, 2025

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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.

@opokornyy
Copy link
Contributor

opokornyy commented Oct 27, 2025

/backport-risk-assessed
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 27, 2025
@opokornyy
Copy link
Contributor

opokornyy commented Oct 27, 2025

/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 Oct 27, 2025
@BaiyangZhou
Copy link

BaiyangZhou commented Oct 28, 2025

/verified by @BaiyangZhou

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 28, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 28, 2025

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

In response to this:

/verified by @BaiyangZhou

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.

@BaiyangZhou
Copy link

BaiyangZhou commented Oct 28, 2025

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 28, 2025
@opokornyy
Copy link
Contributor

opokornyy commented Oct 30, 2025

/approve

@openshift-ci
Copy link

openshift-ci bot commented Oct 30, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ncaak, openshift-cherrypick-robot, opokornyy

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

The pull request process is described here

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 Oct 30, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit ad51ca8 into openshift:release-4.17 Oct 30, 2025
9 checks passed
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 30, 2025

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-63500
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-63500 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

This is an automated cherry-pick of #1123

/assign opokornyy

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-merge-robot
Copy link
Contributor

openshift-merge-robot commented Nov 3, 2025

Fix included in accepted release 4.17.0-0.nightly-2025-11-03-182249

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

Reviewers

@tremes tremes Awaiting requested review from tremes

@BaiyangZhou BaiyangZhou Awaiting requested review from BaiyangZhou

1 more reviewer

@ncaak ncaak ncaak approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@opokornyy opokornyy

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@openshift-cherrypick-robot @openshift-ci-robot @opokornyy @BaiyangZhou @openshift-merge-robot @ncaak