[release-5.0] OCPBUGS-120694: Installed Operators page fails with catalogsources "forbidden ... at the cluster scope" error by platex-rehor-bot · Pull Request #17142 · openshift/console

platex-rehor-bot · 2026-09-03T19:24:47Z

Bug

OCPBUGS-120694

Backport of OCPBUGS-111081 to release-5.0.
Original fix: #17072

Changes

Cherry-picked from main (2 commits).

/jira cherrypick OCPBUGS-120694

OCPBUGS-111081 When the Firehose component was replaced by hooks in MultiListPage (CONSOLE-5026), the loadError computation lost the check that excluded resources declared with optional: true from contributing to the page's fatal error. This caused the Installed Operators page to show a "catalogsources forbidden" error for users whose RBAC is delivered via namespace-scoped RoleBindings only, since the cluster-scoped CatalogSource fetch (declared optional) would fail and its error would be promoted to a fatal page error. The fix cross-references each watched resource's key against the watchResources input config to check the optional flag, restoring the 4.21 behavior where optional resource errors are silently tolerated. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

OCPBUGS-111081 Fix Prettier formatting violation in loadError useMemo (single-line condition). Revert MAX_WARNINGS from 343 back to 342 since this PR does not change the ESLint warning count.

openshift-merge-bot · 2026-09-03T19:24:49Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

openshift-ci-robot · 2026-09-03T19:24:54Z

@platex-rehor-bot: This pull request references Jira Issue OCPBUGS-120694, which is invalid:

expected the bug to target the "5.0.0" version, but no target version was set
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.

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:

Bug

OCPBUGS-120694

Backport of OCPBUGS-111081 to release-5.0.
Original fix: #17072

Changes

Cherry-picked from main (2 commits).

/jira cherrypick OCPBUGS-120694

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.

coderabbitai · 2026-09-03T19:24:55Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: f06ba593-04b7-472c-a079-c543b23d3862

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

_{Comment @coderabbitai help to get the list of available commands.}

openshift-ci · 2026-09-03T19:25:10Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: platex-rehor-bot
Once this PR has been reviewed and has the lgtm label, please assign spadgett for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

frontend/OWNERS

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

openshift-ci · 2026-09-03T19:25:18Z

Hi @platex-rehor-bot. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

platex-rehor-bot · 2026-09-03T19:32:30Z

/jira refresh

openshift-ci-robot · 2026-09-03T19:32:35Z

@platex-rehor-bot: This pull request references Jira Issue OCPBUGS-120694, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-111081 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-111081 targets the "5.1.0" version, which is one of the valid target versions: 5.1.0
bug has dependents

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.

jhadvig · 2026-09-04T09:01:16Z

/ok-to-test

platex-rehor-bot · 2026-09-04T09:41:05Z

/retest

openshift-ci · 2026-09-04T09:54:27Z

@platex-rehor-bot: 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/frontend	`913ca3e`	link	true	`/test frontend`
ci/prow/images	`913ca3e`	link	true	`/test images`
ci/prow/analyze	`913ca3e`	link	true	`/test analyze`

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.

platex-rehor-bot and others added 2 commits September 3, 2026 19:24

fix(list-page): fix Prettier formatting and revert MAX_WARNINGS

913ca3e

OCPBUGS-111081 Fix Prettier formatting violation in loadError useMemo (single-line condition). Revert MAX_WARNINGS from 343 back to 342 since this PR does not change the ESLint warning count.

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 Sep 3, 2026

openshift-ci Bot requested review from jhadvig and sg00dwin September 3, 2026 19:25

openshift-ci Bot added the component/core Related to console core functionality label Sep 3, 2026

openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Sep 3, 2026

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 Sep 3, 2026

openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 4, 2026

Navigation Menu

Uh oh!

[release-5.0] OCPBUGS-120694: Installed Operators page fails with catalogsources "forbidden ... at the cluster scope" error - #17142

[release-5.0] OCPBUGS-120694: Installed Operators page fails with catalogsources "forbidden ... at the cluster scope" error#17142
platex-rehor-bot wants to merge 2 commits into
openshift:release-5.0from
platex-rehor-bot:bot/OCPBUGS-120694

platex-rehor-bot commented Sep 3, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 3, 2026

Uh oh!

openshift-ci-robot commented Sep 3, 2026

Bug

Changes

Uh oh!

coderabbitai Bot commented Sep 3, 2026

Review skipped

Uh oh!

openshift-ci Bot commented Sep 3, 2026

Uh oh!

openshift-ci Bot commented Sep 3, 2026

Uh oh!

platex-rehor-bot commented Sep 3, 2026

Uh oh!

openshift-ci-robot commented Sep 3, 2026

Uh oh!

jhadvig commented Sep 4, 2026

Uh oh!

platex-rehor-bot commented Sep 4, 2026

Uh oh!

openshift-ci Bot commented Sep 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

platex-rehor-bot commented Sep 3, 2026

Bug

Changes

Uh oh!

openshift-merge-bot Bot commented Sep 3, 2026

Uh oh!

openshift-ci-robot commented Sep 3, 2026

Bug

Changes

Uh oh!

coderabbitai Bot commented Sep 3, 2026

Review skipped

Uh oh!

openshift-ci Bot commented Sep 3, 2026

Uh oh!

openshift-ci Bot commented Sep 3, 2026

Uh oh!

platex-rehor-bot commented Sep 3, 2026

Uh oh!

openshift-ci-robot commented Sep 3, 2026

Uh oh!

jhadvig commented Sep 4, 2026

Uh oh!

platex-rehor-bot commented Sep 4, 2026

Uh oh!

openshift-ci Bot commented Sep 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants