MULTIARCH-5190: Promote ImageStreamImportMode to default by Prashanth684 · Pull Request #2266 · openshift/api

Prashanth684 · 2025-04-09T12:21:48Z

The ImageStreamImportMode feature gate was introduced in 4.18 and tests were added around the 4.19 timeframe. The feature has been tested for a while now and the sippy dashboard looks healthy. There are 3 tests that were added to exercise the testing of this feature.

openshift-ci-robot · 2025-04-09T12:21:52Z

@Prashanth684: This pull request references MULTIARCH-5190 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

The ImageStreamImportMode feature gate was introduced in 4.18 and tests were added around the 4.19 timeframe. The feature has been tested for a while now and the sippy dashboard looks healthy. There are 3 tests that were added to exercise the testing of this feature.

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 · 2025-04-09T12:21:54Z

Hello @Prashanth684! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

Prashanth684 · 2025-04-10T06:10:31Z

verify-feature-promotion is failing with:

F0409 12:32:19.597966   10476 root.go:64] Error running codegen: error: only 0 tests found, need at least 5 for "ImageStreamImportMode" on {metal amd64 ha dual}
error: only 2 tests found, need at least 5 for "ImageStreamImportMode" on {aws amd64 ha }
error: only 2 tests found, need at least 5 for "ImageStreamImportMode" on {azure amd64 ha }
error: only 2 tests found, need at least 5 for "ImageStreamImportMode" on {gcp amd64 ha }
error: only 2 tests found, need at least 5 for "ImageStreamImportMode" on {vsphere amd64 ha }
error: only 0 tests found, need at least 5 for "ImageStreamImportMode" on {metal amd64 ha ipv4}
error: only 0 tests found, need at least 5 for "ImageStreamImportMode" on {metal amd64 ha ipv6}

The tests that were added seem to not be running for baremetal - not sure why that's the case. This feature is platform agnostic though so it shouldn't matter. There are 3 tests defined, but only 2 run because the importmode field already has the default Legacy set for all clusters today, so for a single arch cluster, the test that toggles the field to legacy will be skipped.

Prashanth684 · 2025-04-10T06:25:05Z

/cc @JoelSpeed

is it a hard and fast requirement to have "5" tests ?

JoelSpeed · 2025-04-10T10:30:39Z

Could we see if we can work out why these aren't running on metal?

JoelSpeed · 2025-04-10T10:31:45Z

is it a hard and fast requirement to have "5" tests ?

Generally the expectation is that it shouldn't be too hard to write 5 tests for a feature. In this case, can you explain the test cases you have, and why they completely cover the feature and additional tests should not be needed?

Prashanth684 · 2025-04-12T14:18:06Z

is it a hard and fast requirement to have "5" tests ?

Generally the expectation is that it shouldn't be too hard to write 5 tests for a feature. In this case, can you explain the test cases you have, and why they completely cover the feature and additional tests should not be needed?

The ImportMode default used to be Legacy. With this feature:

The default for ImportMode depends on the CV's status.Desired.Architecture
The default can also be changed through a knob in the images.config.openshift.io, ImageStreamImportMode which can be set to Legacy or PreserveOriginal.

There are three test cases. All the test cases check the value of ImportMode in a created imagestream tag's ImportPolicy.

The first test checks that for an imagestream that is created, the ImportMode in the tag's ImportPolicy is set based on the ClusterVersion's desired.Architecture field in its status (if arch == Multi, the importMode should be PreserveOriginal, if not it should be Legacy)
The second test checks that when the image config's ImageStreamImportMode is changed to Legacy (when the default is not Legacy), a newly created imagestream's ImportMode is also set to Legacy.
The third test checks that when the image config's ImageStreamImportMode is changed to PreserveOriginal (when the default is not PreserveOriginal), a newly created imagestream's ImportMode is also set to PreserveOriginal.

Only two tests run due to the first part of the feature where the default import mode is set based on the CV's architecture in the desired status.

Prashanth684 · 2025-04-12T16:00:58Z

Could we see if we can work out why these aren't running on metal?

ah.. i think it's because they are part of the serial test suite and metal only runs the parallel test suite:

[sig-imageregistry][OCPFeatureGate:ImageStreamImportMode][Serial] ImageStream API import mode should be PreserveOriginal or Legacy depending on desired.architecture field in the CV [apigroup:image.openshift.io] [Suite:openshift/conformance/serial]

JoelSpeed · 2025-04-14T16:14:39Z

/retest

JoelSpeed · 2025-04-17T09:02:22Z

/retest

JoelSpeed · 2025-04-22T11:44:56Z

/override ci/prow/verify-crd-schema

Existing failure that cannot be resolved now

JoelSpeed · 2025-04-22T11:45:52Z

i think it's because they are part of the serial test suite and metal only runs the parallel test suite:

Metal runs the serial suite for the stable featureset, but doesn't currently for tech preview, this should be fixed so that we can get signal

openshift-ci · 2025-04-22T11:46:27Z

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-crd-schema

Details

In response to this:

/override ci/prow/verify-crd-schema

Existing failure that cannot be resolved now

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.

wewang58 · 2025-06-12T02:48:27Z

Some jobs are failed, when will the pr can be merged? thanks

JoelSpeed · 2025-06-12T10:37:39Z

/test verify-feature-promotion

JoelSpeed · 2025-06-12T11:08:43Z

We need to get more data according to the verify feature promotion job, any idea why one of the tests has such infrequent runs compared to the others? We are looking for at least 14 runs, and a 95% pass rate across the tests

Prashanth684 · 2025-06-12T16:57:44Z

We need to get more data according to the verify feature promotion job, any idea why one of the tests has such infrequent runs compared to the others? We are looking for at least 14 runs, and a 95% pass rate across the tests

As discussed, I enabled the one test which was consistently being skipped and added another test to check the arch field in the clusterversion: openshift/origin#29808. The sippy dashboard for the featuregate now shows consistent runs for the tests - the one added recently needs some more runs, but eventually it should also have good signal. There are a few reds i see and these are:

the tests which toggle the import mode need to be skipped on SNO as they cause API server disruptions which SNO doesn't do well with (observed config changes, so apiserver needs to restart)
the metal tests failures seem to be due to a certificate issue which the metal team is looking into
the gcp failures seem to be a wider issue in the cluster with many tests failing (doesn't seem related to these tests)

Prashanth684 · 2025-06-12T16:59:49Z

We need to get more data according to the verify feature promotion job, any idea why one of the tests has such infrequent runs compared to the others? We are looking for at least 14 runs, and a 95% pass rate across the tests

As discussed, I enabled the one test which was consistently being skipped and added another test to check the arch field in the clusterversion: openshift/origin#29808. The sippy dashboard for the featuregate now shows consistent runs for the tests - the one added recently needs some more runs, but eventually it should also have good signal. There are a few reds i see and these are:

the tests which toggle the import mode need to be skipped on SNO as they cause API server disruptions which SNO doesn't do well with (observed config changes, so apiserver needs to restart)

the metal tests failures seem to be due to a certificate issue which the metal team is looking into

the gcp failures seem to be a wider issue in the cluster with many tests failing (doesn't seem related to these tests)

this brings the test count to 4 - one short of 5 - but maybe after seeing consistent runs of these tests, we can make an exception?

Prashanth684 · 2025-08-04T20:24:53Z

@JoelSpeed revisiting this again after fixing some failing tests - the board looks green overall for this featuregate. The verify-feature-promotion will still fail as there are only 4 tests associated with the feature. Can we make an exception for this ?

JoelSpeed · 2025-08-06T15:15:34Z

@Prashanth684 are you confident that the 4 tests you have are sufficient for covering the entire feature here? There's no gaps in the testing that you're aware of?

Can we get this PR rebased and get a fresh run of the verify-feature-promotion check

Prashanth684 · 2025-08-06T23:21:02Z

@Prashanth684 are you confident that the 4 tests you have are sufficient for covering the entire feature here? There's no gaps in the testing that you're aware of?

Can we get this PR rebased and get a fresh run of the verify-feature-promotion check

Yes, the feature is tested in its entirety through the 4 tests. In addition to the three tests mentioned here, the 4th test also checks the CVO's desired.Status.Architecture field to check if it is set appropriately when the release paylaod is multi vs single.

JoelSpeed · 2025-08-07T10:31:39Z

@Prashanth684 Is this feature expected to be supported on SNO?

Can we gangway trigger 5 metal runs to boost the stats there and show we are passing with at least 14 runs?

coderabbitai · 2025-11-19T15:15:15Z

Walkthrough

Removes Image CRD manifests, adds an optional architecture field to the ClusterVersion CRD schema, moves ImageStreamImportMode to enabled in feature-gate payloads, and expands two feature gates to include the Default configuration.

Changes

Cohort / File(s)	Summary
ClusterVersion CRD Schema Updates `config/v1/zz_generated.crd-manifests/0000_00_cluster-version-operator_01_clusterversions-Default.crd.yaml`	Added optional `architecture` (string) with enum values `Multi` and `""` in multiple schema locations: `status.availableUpdates` releases, `spec.desiredUpdate`, and `spec.desired`.
Image CRD Deletions (config/v1) `config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images-Default.crd.yaml`, `config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images-DevPreviewNoUpgrade.crd.yaml`, `config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images-TechPreviewNoUpgrade.crd.yaml`	Removed full CustomResourceDefinition manifests for `images.config.openshift.io` (group `config.openshift.io`, kind `Image`, version `v1`) including full OpenAPI v3 schemas, spec/status fields, validations, and subresources.
Image CRD Annotation Removal `config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images.crd.yaml`, `payload-manifests/crds/0000_10_config-operator_01_images.crd.yaml`	Removed metadata annotation `release.openshift.io/feature-set: CustomNoUpgrade` from images CRD manifest(s).
Image CRD Deletions (payload-manifests) `payload-manifests/crds/0000_10_config-operator_01_images-Default.crd.yaml`, `payload-manifests/crds/0000_10_config-operator_01_images-DevPreviewNoUpgrade.crd.yaml`, `payload-manifests/crds/0000_10_config-operator_01_images-TechPreviewNoUpgrade.crd.yaml`	Deleted payload CRD files defining `images.config.openshift.io` with comprehensive schemas, nested structures, validations, and status fields.
Feature Gate Code Updates `features/features.go`	Updated `FeatureGateConsolePluginCSP` and `FeatureGateImageStreamImportMode` initializations to include `configv1.Default` in `enableIn(...)` alongside `DevPreviewNoUpgrade` and `TechPreviewNoUpgrade`.
Feature Gate Status Updates (payloads) `payload-manifests/featuregates/featureGate-Hypershift-Default.yaml`, `payload-manifests/featuregates/featureGate-SelfManagedHA-Default.yaml`	Moved `ImageStreamImportMode` from `disabled` to `enabled` arrays in FeatureGate status definitions.
Documentation reordering `features.md`	Reordered the `ImageStreamImportMode` table row; content unchanged.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Areas requiring extra attention:

Validate cluster impact of removing images.config.openshift.io CRDs and confirm any migration/compatibility steps for consumers.
Ensure feature-gate scope expansion (adding Default) for ImageStreamImportMode and ConsolePluginCSP is intended and that tests/behaviors are covered.
Confirm ClusterVersion architecture additions are consistent across all uses and documentation reflects the new enum values.

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 088d7cd and 42f4458.

📒 Files selected for processing (13)

config/v1/zz_generated.crd-manifests/0000_00_cluster-version-operator_01_clusterversions-Default.crd.yaml (3 hunks)
config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images-Default.crd.yaml (0 hunks)
config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images-DevPreviewNoUpgrade.crd.yaml (0 hunks)
config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images-TechPreviewNoUpgrade.crd.yaml (0 hunks)
config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images.crd.yaml (0 hunks)
features.md (1 hunks)
features/features.go (1 hunks)
payload-manifests/crds/0000_10_config-operator_01_images-Default.crd.yaml (0 hunks)
payload-manifests/crds/0000_10_config-operator_01_images-DevPreviewNoUpgrade.crd.yaml (0 hunks)
payload-manifests/crds/0000_10_config-operator_01_images-TechPreviewNoUpgrade.crd.yaml (0 hunks)
payload-manifests/crds/0000_10_config-operator_01_images.crd.yaml (0 hunks)
payload-manifests/featuregates/featureGate-Hypershift-Default.yaml (1 hunks)
payload-manifests/featuregates/featureGate-SelfManagedHA-Default.yaml (1 hunks)

💤 Files with no reviewable changes (8)

payload-manifests/crds/0000_10_config-operator_01_images.crd.yaml
config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images.crd.yaml
payload-manifests/crds/0000_10_config-operator_01_images-DevPreviewNoUpgrade.crd.yaml
config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images-TechPreviewNoUpgrade.crd.yaml
payload-manifests/crds/0000_10_config-operator_01_images-TechPreviewNoUpgrade.crd.yaml
config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images-DevPreviewNoUpgrade.crd.yaml
config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_images-Default.crd.yaml
payload-manifests/crds/0000_10_config-operator_01_images-Default.crd.yaml

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

payload-manifests/featuregates/featureGate-SelfManagedHA-Default.yaml
features.md
features/features.go
config/v1/zz_generated.crd-manifests/0000_00_cluster-version-operator_01_clusterversions-Default.crd.yaml

🧰 Additional context used

📓 Path-based instructions (1)

**

⚙️ CodeRabbit configuration file

-Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity.

Files:

payload-manifests/featuregates/featureGate-Hypershift-Default.yaml

🔇 Additional comments (1)

payload-manifests/featuregates/featureGate-Hypershift-Default.yaml (1)

278-280: LGTM!

The change correctly promotes ImageStreamImportMode to the enabled list with proper alphabetical placement. The JSON syntax is valid and consistent with surrounding feature gate entries. This aligns with the broader promotion of ImageStreamImportMode across default configurations as documented in the PR.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.5.0)

Error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented
The command is terminated due to an error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

Provide your own instructions using the high_level_summary_instructions setting.
Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

📝 Description — Summarize the main change in 50–60 words, explaining what was done.

📓 References — List relevant issues, discussions, documentation, or related PRs.

📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.

📊 Contributor Summary — Include a Markdown table showing contributions:
| Contributor | Lines Added | Lines Removed | Files Changed |

✔️ Additional Notes — Add any extra reviewer context.
Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

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

Prashanth684 · 2025-11-19T19:54:18Z

/test verify-feature-promotion

Prashanth684 · 2025-11-20T06:17:59Z

/test verify-feature-promotion

Prashanth684 · 2025-11-23T19:11:32Z

/test verify-feature-promotion

The ImageStreamImportMode feature gate was introduced in 4.18 and tests were added around the 4.19 timeframe. The feature has been tested for a while now and the sippy dashboard looks healthy. There are 3 tests which were added to exercise the testing of this feature.

openshift-ci · 2025-11-24T18:55:34Z

@Prashanth684: 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-aws-serial-techpreview	`49d3888`	link	true	`/test e2e-aws-serial-techpreview`

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.

everettraven · 2025-11-25T13:53:09Z

Promotion verification is failing on 4/5 tests but it has been confirmed that 4 tests is sufficient to fully test this feature.

@sdodson ACKed that this is OK to merge post "pencils down".

/override ci/prow/verify-feature-promotion
/lgtm

sdodson · 2025-11-25T13:53:48Z

/pipeline required

openshift-ci-robot · 2025-11-25T13:53:52Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change

sdodson · 2025-11-25T13:55:01Z

/verified by CI
/label approved

openshift-ci-robot · 2025-11-25T13:55:13Z

@sdodson: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI
/label approved

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 · 2025-11-25T13:55:50Z

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

openshift-ci · 2025-11-25T13:56:34Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven

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~~ [everettraven]

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

openshift-ci · 2025-11-25T13:58:14Z

@everettraven: Overrode contexts on behalf of everettraven: ci/prow/verify-feature-promotion

Details

In response to this:

Promotion verification is failing on 4/5 tests but it has been confirmed that 4 tests is sufficient to fully test this feature.

@sdodson ACKed that this is OK to merge post "pencils down".

/override ci/prow/verify-feature-promotion
/lgtm

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-robot · 2025-11-25T17:09:49Z

/retest-required

Remaining retests: 0 against base HEAD bb4a604 and 2 for PR HEAD 42f4458 in total

The following test was failing for multi clusters: ``` [sig-cluster-lifecycle][OCPFeatureGate:ImageStreamImportMode] ClusterVersion API desired architecture should be valid when architecture is set in release payload metadata [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel] ``` This was because openshift/api#2266 promoted the ImageStreamImportMode featuregate to default, but CVO was not updaing the desired.Architecture status field because it did not exist in the CRD.

neisw · 2025-12-08T11:42:01Z

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-upgrade-fips 10

openshift-ci · 2025-12-08T11:42:05Z

@neisw: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-upgrade-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e9f2e510-d42a-11f0-956b-1d9cdb7038d8-0

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 9, 2025

openshift-ci Bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Apr 9, 2025

openshift-ci Bot requested review from deads2k and everettraven April 9, 2025 12:22

openshift-ci Bot requested a review from JoelSpeed April 10, 2025 06:25

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 4, 2025

Prashanth684 force-pushed the api-importmode-default branch from 49d3888 to 7d6dded Compare August 6, 2025 23:18

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 6, 2025

Prashanth684 force-pushed the api-importmode-default branch from 668769f to 088d7cd Compare November 19, 2025 15:15

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 23, 2025

Prashanth684 force-pushed the api-importmode-default branch from 088d7cd to 42f4458 Compare November 24, 2025 16:09

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 24, 2025

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

openshift-ci Bot assigned everettraven Nov 25, 2025

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

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 25, 2025

sdodson merged commit 5cf710f into openshift:master Nov 25, 2025
25 of 28 checks passed

jianlinliu mentioned this pull request Nov 27, 2025

WIP: Revert "MULTIARCH-5190: Promote ImageStreamImportMode to default" #2605

Closed

Prashanth684 mentioned this pull request Dec 1, 2025

OCPBUGS-66215: update o/api vendoring openshift/cluster-version-operator#1269

Merged

neisw mentioned this pull request Dec 10, 2025

Revert "MULTIARCH-5190: Promote ImageStreamImportMode to default" #2617

Closed

Conversation

Prashanth684 commented Apr 9, 2025

Uh oh!

openshift-ci-robot commented Apr 9, 2025 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci Bot commented Apr 9, 2025

Uh oh!

Prashanth684 commented Apr 10, 2025

Uh oh!

Prashanth684 commented Apr 10, 2025

Uh oh!

JoelSpeed commented Apr 10, 2025

Uh oh!

JoelSpeed commented Apr 10, 2025

Uh oh!

Prashanth684 commented Apr 12, 2025

Uh oh!

Prashanth684 commented Apr 12, 2025

Uh oh!

JoelSpeed commented Apr 14, 2025

Uh oh!

JoelSpeed commented Apr 17, 2025

Uh oh!

JoelSpeed commented Apr 22, 2025

Uh oh!

JoelSpeed commented Apr 22, 2025

Uh oh!

openshift-ci Bot commented Apr 22, 2025

Uh oh!

wewang58 commented Jun 12, 2025

Uh oh!

JoelSpeed commented Jun 12, 2025

Uh oh!

JoelSpeed commented Jun 12, 2025

Uh oh!

Prashanth684 commented Jun 12, 2025

Uh oh!

Prashanth684 commented Jun 12, 2025

Uh oh!

Prashanth684 commented Aug 4, 2025

Uh oh!

JoelSpeed commented Aug 6, 2025

Uh oh!

Prashanth684 commented Aug 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JoelSpeed commented Aug 7, 2025

Uh oh!

coderabbitai Bot commented Nov 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Uh oh!

Prashanth684 commented Nov 19, 2025

Uh oh!

Prashanth684 commented Nov 20, 2025

Uh oh!

Prashanth684 commented Nov 23, 2025

Uh oh!

openshift-ci Bot commented Nov 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

everettraven commented Nov 25, 2025

Uh oh!

sdodson commented Nov 25, 2025

Uh oh!

openshift-ci-robot commented Nov 25, 2025

Uh oh!

sdodson commented Nov 25, 2025

Uh oh!

openshift-ci-robot commented Nov 25, 2025

Uh oh!

openshift-ci-robot commented Nov 25, 2025

Uh oh!

openshift-ci Bot commented Nov 25, 2025

Uh oh!

openshift-ci Bot commented Nov 25, 2025

Uh oh!

openshift-ci-robot commented Apr 9, 2025 •

edited by openshift-ci Bot

Loading

Prashanth684 commented Aug 6, 2025 •

edited

Loading

coderabbitai Bot commented Nov 19, 2025 •

edited

Loading

openshift-ci Bot commented Nov 24, 2025 •

edited

Loading