[release-5.0] OCPBUGS-114388: display operators in catalog when Tech Preview enabled - #17100
Conversation
useCatalogItems returned `loading = true` (in progress) as the second element of its tuple, but CatalogExtensionHookResolver treats the second element as `loaded = true` (ready). This caused the catalog to call onValueResolved immediately with an empty array, then never again once real items arrived from /api/olm/catalog-items/. Rename `loading` to `loaded` and invert the initial state (false → true on completion) in both useCatalogItems and useCatalogCategories. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The OLMv0 console.catalog/item-type for "operator" had no flag guard, causing it to remain active alongside the OLMv1 item-type when OLMV1_ENABLED=true. This produced a duplicate "Operators" entry in the catalog type selector. Add the same disallowed: [OLMV1_ENABLED] flag that already gates the OLMv0 item-provider, so only the OLMv1 item-type is active when OLMv1 is enabled. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ering Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
/uncc |
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-85646 has been cloned as Jira Issue OCPBUGS-114388. Will retitle bug to link to clone. DetailsIn response to this:
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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-114388, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
/lgtm |
|
Scheduling tests matching the |
logonoff
left a comment
There was a problem hiding this comment.
/label backport-risk-assessed
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: logonoff, openshift-cherrypick-robot, simkam The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@openshift-cherrypick-robot: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/label approved |
|
/cherry-pick release-4.22 |
|
@sdodson: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
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. |
|
@sdodson: This PR has been marked as verified by DetailsIn response to this:
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. |
f632d1e
into
openshift:release-5.0
|
@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-114388 Jira Issue OCPBUGS-114388 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
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. |
|
@sdodson: #17100 failed to apply on top of branch "release-4.22": DetailsIn response to this:
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. |
|
Fix included in release 5.0.0-0.nightly-2026-08-27-222048 |
This is an automated cherry-pick of #16976
/assign sdodson