OCPBUGS-85646: display operators in catalog when Tech Preview enabled by simkam · Pull Request #16976 · openshift/console

simkam · 2026-08-13T09:11:37Z

https://redhat.atlassian.net/browse/OCPBUGS-85646

Analysis / Root cause:
useCatalogItems returned [items, loading, error] but CatalogExtensionHookResolver expects [data, loaded, error]. The inverted boolean semantics caused the catalog to report 0 items as "resolved" immediately and ignore real data when it arrived.

Solution description:

Fix inverted loaded/loading state — Rename loading → loaded and invert initial state in useCatalogItems and useCatalogCategories
Fix duplicate catalog type — Add disallowed: [OLMV1_ENABLED] flag to OLMv0 operator item-type to prevent both OLMv0 and OLMv1 types appearing simultaneously
Add regression test — Playwright e2e test with mocked API to verify operator tiles render correctly

Screenshots / screen recording:
Before (no operators)

After:

Test setup:

Test cases:
Playwright tests included.

Browser conformance:

Chrome
Firefox
Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

Summary by CodeRabbit

Bug Fixes
- Improved catalog loading behavior so categories and items accurately report when data has finished loading, including error scenarios.
- Added configuration to hide the operator catalog when the OLM v1 experience is enabled.
Tests
- Added coverage for catalog loading, polling, normalization, successful fetches, and errors.
- Added regression tests for displaying, filtering, and restoring operator catalog tiles.
- Expanded end-to-end test coverage for catalog and operator lifecycle metadata.

openshift-merge-bot · 2026-08-13T09:11:42Z

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-08-13T09:11:45Z

@simkam: This pull request references Jira Issue OCPBUGS-85646, which is invalid:

expected the bug to target either version "5.0.0." or "openshift-5.0.0.", but it targets "4.22" 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:

https://redhat.atlassian.net/browse/OCPBUGS-85646

Analysis / Root cause:
useCatalogItems returned [items, loading, error] but CatalogExtensionHookResolver expects [data, loaded, error]. The inverted boolean semantics caused the catalog to report 0 items as "resolved" immediately and ignore real data when it arrived.

Solution description:

Fix inverted loaded/loading state — Rename loading → loaded and invert initial state in useCatalogItems and useCatalogCategories

Fix duplicate catalog type — Add disallowed: [OLMV1_ENABLED] flag to OLMv0 operator item-type to prevent both OLMv0 and OLMv1 types appearing simultaneously

Add regression test — Playwright e2e test with mocked API to verify operator tiles render correctly

Screenshots / screen recording:
Before (no operators)

After:

Test setup:

Test cases:
Playwright tests included.

Browser conformance:

Chrome

Firefox

Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

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-08-13T09:12:01Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: f5dc3cc6-3847-43d3-b7b7-55db4e294327

📥 Commits

Reviewing files that changed from the base of the PR and between f2910bc and 527795f.

📒 Files selected for processing (2)

frontend/e2e/tests/dev-console/catalog.spec.ts
test-prow-playwright-e2e-techpreview.sh

🚧 Files skipped from review as they are similar to previous changes (2)

test-prow-playwright-e2e-techpreview.sh
frontend/e2e/tests/dev-console/catalog.spec.ts

Included review availability: Your plan includes up to 2 reviews per rolling hour; 1 remains after this review.

Walkthrough

The catalog hooks replace loading with loaded, keep categories empty until catalog loading completes, gate the operator catalog item with OLMV1_ENABLED, and add unit and Playwright coverage.

Changes

Catalog flow

Layer / File(s)	Summary
Catalog loaded-state contract `frontend/packages/operator-lifecycle-manager-v1/src/hooks/useCatalogItems.ts`, `frontend/packages/operator-lifecycle-manager-v1/src/hooks/useCatalogCategories.ts`, `frontend/packages/operator-lifecycle-manager-v1/src/hooks/__tests__/useCatalogItems.spec.ts`	`useCatalogItems` exposes `loaded` after successful or non-abort failed fetches. `useCatalogCategories` consumes this state and returns no categories until loading completes or when an error exists. Unit tests cover the fetch states.
Operator catalog gating and end-to-end coverage `frontend/packages/operator-lifecycle-manager/console-extensions.json`, `frontend/e2e/tests/dev-console/catalog.spec.ts`, `test-prow-playwright-e2e-techpreview.sh`	The operator catalog item is disallowed when `OLMV1_ENABLED` is set. Playwright tests cover operator visibility and filtering. The tech-preview script runs the catalog specification.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Merge Risk: ⚪ Minimal · up to 52779

The PR corrects operator catalog loading and duplicate type handling and adds regression coverage; no actionable merge-blocking risk remains beyond normal checks and review.

Suggested reviewers: spadgett, therealjon

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the Jira issue and the primary change: displaying operators when OLMv1 Tech Preview is enabled.
Description check	✅ Passed	The description covers the root cause, solution, screenshots, and regression test, but leaves test setup and browser conformance incomplete.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The PR adds only static Jest and Playwright test titles. The changed lines contain no Ginkgo titles or dynamic values such as timestamps, UUIDs, namespaces, nodes, or IPs.
Test Structure And Quality	✅ Passed	Changed tests are TypeScript Jest and Playwright files; the diff introduces no Ginkgo test code or Ginkgo cluster operations, so this check is not applicable.
Microshift Test Compatibility	✅ Passed	The PR adds Playwright TypeScript and Jest tests, not Ginkgo e2e tests; the MicroShift API compatibility check does not apply.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR adds Playwright and Jest TypeScript tests only; it adds no Ginkgo e2e tests or multi-node/HA assumptions covered by this check.
Topology-Aware Scheduling Compatibility	✅ Passed	The PR changes only catalog UI hooks, extension metadata, tests, and a test script; the diff adds no deployment, controller, replica, affinity, topology, nodeSelector, toleration, or PDB scheduling...
Ote Binary Stdout Contract	✅ Passed	The PR changes only TypeScript, JSON, and a Playwright shell entrypoint; no OTE Go process-level code or stdout writes were added.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The PR adds Playwright and Jest tests, not Ginkgo e2e tests. They use relative console routes or mocked fetches and contain no hardcoded IPv4 addresses or public internet endpoints.
No-Weak-Crypto	✅ Passed	The full PR diff adds no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, crypto API, custom crypto, or secret-comparison code.
Container-Privileges	✅ Passed	The PR diff contains no container/Kubernetes manifests and adds no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR adds no logging of sensitive data. Added tests use fixed non-sensitive values, and the existing kubeadmin password export remains protected by `set +x`.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

simkam · 2026-08-13T09:12:55Z

/jira refresh

openshift-ci-robot · 2026-08-13T09:12:57Z

@simkam: This pull request references Jira Issue OCPBUGS-85646, 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 (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

https://redhat.atlassian.net/browse/OCPBUGS-85646

Analysis / Root cause:
useCatalogItems returned [items, loading, error] but CatalogExtensionHookResolver expects [data, loaded, error]. The inverted boolean semantics caused the catalog to report 0 items as "resolved" immediately and ignore real data when it arrived.

Solution description:

Fix inverted loaded/loading state — Rename loading → loaded and invert initial state in useCatalogItems and useCatalogCategories

Fix duplicate catalog type — Add disallowed: [OLMV1_ENABLED] flag to OLMv0 operator item-type to prevent both OLMv0 and OLMv1 types appearing simultaneously

Add regression test — Playwright e2e test with mocked API to verify operator tiles render correctly

Screenshots / screen recording:
Before (no operators)

After:

Test setup:

Test cases:
Playwright tests included.

Browser conformance:

Chrome

Firefox

Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

Summary by CodeRabbit

New Features

Added operator catalog support for displaying operator tiles, empty states, and keyword filtering.

Added catalog data for multiple operators, including descriptions, versions, providers, and capabilities.

Bug Fixes

Improved catalog loading behavior so empty and error states are handled correctly.

Prevented the legacy operator catalog from appearing when the OLMv1 experience is enabled.

Tests

Added end-to-end coverage for catalog rendering, filtering, and empty-state behavior.

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-robot · 2026-08-13T09:12:59Z

@simkam: This pull request references Jira Issue OCPBUGS-85646, which is valid.

3 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)

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.

sampadasawant-36

Reviewed the diff — the fix looks correct overall. A couple of observations:

The core fix is right — inverting loading: true → loaded: false and updating the guard in useCatalogCategories (if (loading || error) → if (!loaded || error)) properly aligns with what CatalogExtensionHookResolver expects. The OLMV1_ENABLED disallowed flag in console-extensions.json also makes sense to avoid duplicate catalog entries.

Two minor suggestions:

Unit test for the hook — The semantic inversion (loading → loaded) is the heart of the fix but is only covered by e2e. A unit test for useCatalogItems that verifies loaded starts as false and transitions to true on fetch completion (and on error) would protect against regression without needing a cluster.
test.skip inside beforeEach — This works in Playwright but the idiomatic pattern is to call test.skip(condition, reason) at the top of each test rather than inside the hook. Calling it in beforeEach can sometimes produce misleading output when multiple tests are skipped.

Otherwise the e2e mock approach using page.route() is clean and the test coverage of filtering is a nice addition. LGTM from a logic standpoint!

simkam · 2026-08-14T10:08:01Z

updated per review - added unit tests, moved skip logic in e2e

simkam · 2026-08-14T13:30:58Z

/test e2e-gcp-console
/test e2e-playwright

simkam · 2026-08-14T16:23:01Z

/test e2e-playwright

simkam · 2026-08-14T19:48:36Z

/test e2e-playwright

simkam · 2026-08-16T14:33:24Z

/test e2e-playwright

simkam · 2026-08-17T07:40:58Z

/test e2e-playwright

stefanonardo · 2026-08-17T09:24:57Z

@coderabbitai review

coderabbitai · 2026-08-17T09:25:04Z

⚠️ Action not completed

Already reviewed.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

stefanonardo · 2026-08-17T09:26:36Z

+
+const CATALOG_ITEMS_URL_PATTERN = '**/api/olm/catalog-items/**';
+
+test.describe('OLMv1 Software Catalog items', { tag: ['@admin'] }, () => {


wouldn't it better to put it in the existing catalog.spec.ts to avoid fragmentation?

yes, moved there

stefanonardo · 2026-08-17T09:33:49Z

+
+const CATALOG_ITEMS_URL_PATTERN = '**/api/olm/catalog-items/**';
+
+test.describe('OLMv1 Software Catalog items', { tag: ['@admin'] }, () => {


is this suite actually testing something strictly related to OLMv1 catalog? Is it maybe just testing the generic behavior of the Catalog Page with v1 data?

no, test generalized and moved to catalog.spec.ts.

openshift-merge-bot · 2026-08-24T13:36:02Z

Tests from second stage were triggered manually. Pipeline can be controlled only manually, until HEAD changes. Use command to trigger second stage.

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>

simkam · 2026-08-24T14:12:57Z

/pipeline required

openshift-merge-bot · 2026-08-24T14:13:14Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console
/test e2e-playwright

simkam · 2026-08-24T19:06:36Z

/retest

simkam · 2026-08-24T22:15:36Z

/retest

logonoff · 2026-08-25T01:00:43Z

/unhold
/lgtm
/verified by ci

openshift-ci-robot · 2026-08-25T01:00:54Z

@logonoff: This PR has been marked as verified by ci.

Details

In response to this:

/unhold
/lgtm
/verified by ci

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-bot · 2026-08-25T01:00:57Z

Tests from second stage were triggered manually. Pipeline can be controlled only manually, until HEAD changes. Use command to trigger second stage.

openshift-ci · 2026-08-25T01:01:29Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, simkam, stefanonardo

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:

~~OWNERS~~ [logonoff]

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-08-25T01:28:53Z

@simkam: 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/e2e-playwright	`70b506b`	link	false	`/test e2e-playwright`

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.

openshift-ci-robot · 2026-08-25T01:31:37Z

@simkam: Jira Issue Verification Checks: Jira Issue OCPBUGS-85646
✔️ 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-85646 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

https://redhat.atlassian.net/browse/OCPBUGS-85646

Analysis / Root cause:
useCatalogItems returned [items, loading, error] but CatalogExtensionHookResolver expects [data, loaded, error]. The inverted boolean semantics caused the catalog to report 0 items as "resolved" immediately and ignore real data when it arrived.

Solution description:

Fix inverted loaded/loading state — Rename loading → loaded and invert initial state in useCatalogItems and useCatalogCategories

Fix duplicate catalog type — Add disallowed: [OLMV1_ENABLED] flag to OLMv0 operator item-type to prevent both OLMv0 and OLMv1 types appearing simultaneously

Add regression test — Playwright e2e test with mocked API to verify operator tiles render correctly

Screenshots / screen recording:
Before (no operators)

After:

Test setup:

Test cases:
Playwright tests included.

Browser conformance:

Chrome

Firefox

Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

Summary by CodeRabbit

Bug Fixes

Improved catalog loading behavior so categories and items accurately report when data has finished loading, including error scenarios.

Added configuration to hide the operator catalog when the OLM v1 experience is enabled.

Tests

Added coverage for catalog loading, polling, normalization, successful fetches, and errors.

Added regression tests for displaying, filtering, and restoring operator catalog tiles.

Expanded end-to-end test coverage for catalog and operator lifecycle metadata.

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 · 2026-08-25T17:14:26Z

Fix included in release 5.1.0-0.nightly-2026-08-25-102753

sdodson · 2026-08-26T16:11:30Z

/cherry-pick release-5.0

openshift-cherrypick-robot · 2026-08-26T16:12:16Z

@sdodson: new pull request created: #17100

Details

In response to this:

/cherry-pick release-5.0

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.

openshift-ci Bot requested review from TheRealJon and spadgett August 13, 2026 09:12

openshift-ci Bot added the component/olm Related to OLM label Aug 13, 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 Aug 13, 2026

simkam force-pushed the olmv1 branch from 38638d3 to 88e5100 Compare August 13, 2026 11:05

sampadasawant-36 reviewed Aug 14, 2026

View reviewed changes

simkam force-pushed the olmv1 branch from 88e5100 to d3d5eff Compare August 14, 2026 08:02

stefanonardo reviewed Aug 17, 2026

View reviewed changes

simkam force-pushed the olmv1 branch from d3d5eff to f2910bc Compare August 17, 2026 13:07

openshift-ci-robot added jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. and removed jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 17, 2026

openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 24, 2026

openshift-ci Bot assigned logonoff Aug 24, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 24, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 24, 2026

simkam and others added 3 commits August 24, 2026 15:40

test(olm): add Playwright tests for operator catalog display and filt…

70b506b

…ering Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

simkam force-pushed the olmv1 branch from 1ebf5f3 to 70b506b Compare August 24, 2026 13:41

openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 24, 2026

openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 25, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 25, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2026

openshift-merge-bot Bot merged commit bc711f8 into openshift:main Aug 25, 2026
10 of 11 checks passed

simkam deleted the olmv1 branch August 25, 2026 07:14

openshift-cherrypick-robot mentioned this pull request Aug 26, 2026

[release-5.0] OCPBUGS-114388: display operators in catalog when Tech Preview enabled #17100

Merged

sdodson mentioned this pull request Aug 27, 2026

[release-4.22] OCPBUGS-114725: display operators in catalog when Tech Preview enabled #17103

Open


		const CATALOG_ITEMS_URL_PATTERN = '/api/olm/catalog-items/';

		test.describe('OLMv1 Software Catalog items', { tag: ['@admin'] }, () => {

Uh oh!

Conversation

simkam commented Aug 13, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

openshift-merge-bot Bot commented Aug 13, 2026

Uh oh!

openshift-ci-robot commented Aug 13, 2026

Uh oh!

coderabbitai Bot commented Aug 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

Changes

Uh oh!

simkam commented Aug 13, 2026

Uh oh!

openshift-ci-robot commented Aug 13, 2026

Summary by CodeRabbit

Uh oh!

openshift-ci-robot commented Aug 13, 2026

Uh oh!

sampadasawant-36 left a comment

Choose a reason for hiding this comment

Uh oh!

simkam commented Aug 14, 2026

Uh oh!

simkam commented Aug 14, 2026

Uh oh!

simkam commented Aug 14, 2026

Uh oh!

simkam commented Aug 14, 2026

Uh oh!

simkam commented Aug 16, 2026

Uh oh!

simkam commented Aug 17, 2026

Uh oh!

stefanonardo commented Aug 17, 2026

Uh oh!

coderabbitai Bot commented Aug 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

stefanonardo Aug 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

simkam Aug 17, 2026

Choose a reason for hiding this comment

Uh oh!

stefanonardo Aug 17, 2026

Choose a reason for hiding this comment

Uh oh!

simkam Aug 17, 2026

Choose a reason for hiding this comment

Uh oh!

openshift-merge-bot Bot commented Aug 24, 2026

Uh oh!

simkam commented Aug 24, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 24, 2026

Uh oh!

simkam commented Aug 24, 2026

Uh oh!

simkam commented Aug 24, 2026

Uh oh!

logonoff commented Aug 25, 2026

Uh oh!

openshift-ci-robot commented Aug 25, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 25, 2026

Uh oh!

openshift-ci Bot commented Aug 25, 2026

Uh oh!

openshift-ci Bot commented Aug 25, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Aug 25, 2026

Summary by CodeRabbit

Uh oh!

simkam commented Aug 13, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Aug 13, 2026 •

edited

Loading

coderabbitai Bot commented Aug 17, 2026 •

edited

Loading

stefanonardo Aug 17, 2026 •

edited

Loading