[release-4.19] OCPBUGS-77367,OCPBUGS-77844: Fix ignition-server pod restarts by jparrill · Pull Request #7858 · openshift/hypershift

jparrill · 2026-03-05T10:53:42Z

Summary

Manual backport of [release-4.20] OCPBUGS-77366,OCPBUGS-65682: Fix ignition-server pod restarts #7842 to release-4.19
Implements a mirror availability cache with differential TTL to prevent MIRRORED_RELEASE_IMAGE env var flapping that caused massive deployment regeneration
Removes MIRRORED_RELEASE_IMAGE from the ignition-server deployment (dead code not consumed at runtime)
Removes getRegistryOverrides() which performed non-deterministic live HTTP registry checks during every CPO reconciliation, replacing it with static registry-level overrides from the HostedCluster spec

Fixes

Backport adaptations

The following changes were made beyond the pure cherry-picks to adapt to release-4.19:

support/util/imagemetadata_test.go: Removed unused "fmt" and "os" imports that were residual from the original commit but not referenced in the test code.
control-plane-operator/controllers/hostedcontrolplane/v2/ignitionserver/deployment_test.go: Replaced t.Context() with context.Background() (adding the "context" import), since t.Context() requires Go 1.24 and release-4.19 uses Go 1.23.

All merge conflicts were resolved by accepting the incoming commit version (removal of getRegistryOverrides() and the controller-runtime/pkg/client import).

Test plan

Verify ignition-server deployment no longer sets MIRRORED_RELEASE_IMAGE env var
Verify mirror availability cache works with differential TTL (5min available, 1min unavailable)
Verify deployment remains stable without flapping in disconnected environments
Run unit tests: go test ./support/util/... ./control-plane-operator/controllers/hostedcontrolplane/v2/ignitionserver/...

🤖 Generated with Claude Code

openshift-ci-robot · 2026-03-05T10:53:50Z

@jparrill: This pull request references Jira Issue OCPBUGS-77367, which is invalid:

expected dependent Jira Issue OCPBUGS-77366 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

This pull request references Jira Issue OCPBUGS-77844, which is invalid:

expected Jira Issue OCPBUGS-77844 to depend on a bug targeting a version in 4.20.0, 4.20.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

Summary

Backport of [release-4.20] OCPBUGS-77366,OCPBUGS-65682: Fix ignition-server pod restarts #7842 to release-4.19

Implements a mirror availability cache with differential TTL to prevent MIRRORED_RELEASE_IMAGE env var flapping that caused massive deployment regeneration

Removes MIRRORED_RELEASE_IMAGE from the ignition-server deployment (dead code not consumed at runtime)

Removes getRegistryOverrides() which performed non-deterministic live HTTP registry checks during every CPO reconciliation, replacing it with static registry-level overrides from the HostedCluster spec

Test plan

Verify ignition-server deployment no longer sets MIRRORED_RELEASE_IMAGE env var

Verify mirror availability cache works with differential TTL (5min available, 1min unavailable)

Verify deployment remains stable without flapping in disconnected environments

Run unit tests: go test ./support/util/... ./control-plane-operator/controllers/hostedcontrolplane/v2/ignitionserver/...

Fixes: https://issues.redhat.com/browse/OCPBUGS-77367
Fixes: https://issues.redhat.com/browse/OCPBUGS-77844

🤖 Generated with Claude Code

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-03-05T10:54:00Z

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: Pro

Run ID: f8d30374-8c18-4a95-852a-97cb7c0dc57b

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

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

openshift-ci-robot · 2026-03-05T10:54:04Z

@jparrill: This pull request references Jira Issue OCPBUGS-77367, which is invalid:

expected dependent Jira Issue OCPBUGS-77366 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

This pull request references Jira Issue OCPBUGS-77844, which is invalid:

expected Jira Issue OCPBUGS-77844 to depend on a bug targeting a version in 4.20.0, 4.20.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

In response to this:

Summary

Manual backport of [release-4.20] OCPBUGS-77366,OCPBUGS-65682: Fix ignition-server pod restarts #7842 to release-4.19

Implements a mirror availability cache with differential TTL to prevent MIRRORED_RELEASE_IMAGE env var flapping that caused massive deployment regeneration

Removes MIRRORED_RELEASE_IMAGE from the ignition-server deployment (dead code not consumed at runtime)

Removes getRegistryOverrides() which performed non-deterministic live HTTP registry checks during every CPO reconciliation, replacing it with static registry-level overrides from the HostedCluster spec

Test plan

Verify ignition-server deployment no longer sets MIRRORED_RELEASE_IMAGE env var

Verify mirror availability cache works with differential TTL (5min available, 1min unavailable)

Verify deployment remains stable without flapping in disconnected environments

Run unit tests: go test ./support/util/... ./control-plane-operator/controllers/hostedcontrolplane/v2/ignitionserver/...

Fixes: https://issues.redhat.com/browse/OCPBUGS-77367
Fixes: https://issues.redhat.com/browse/OCPBUGS-77844

🤖 Generated with Claude Code

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 · 2026-03-05T10:54:13Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jparrill

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

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

jparrill · 2026-03-05T15:07:21Z

/jira refresh

openshift-ci-robot · 2026-03-05T15:07:28Z

@jparrill: This pull request references Jira Issue OCPBUGS-77367, which is invalid:

expected dependent Jira Issue OCPBUGS-77366 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

This pull request references Jira Issue OCPBUGS-77844, which is invalid:

expected dependent Jira Issue OCPBUGS-65682 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

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.

… cache Implement a comprehensive mirror availability cache to prevent MIRRORED_RELEASE_IMAGE environment variable flapping that was causing massive deployment regeneration (observed generation: 1,068,097). The cache prevents non-deterministic mirror selection by: - Caching mirror availability results with differential TTL: * Available mirrors: 5 minutes (longer for stability) * Unavailable mirrors: 1 minute (shorter for faster recovery) - Using 15-second timeout for mirror verification - Thread-safe operations with sync.RWMutex - Automatic cleanup of expired entries This resolves the MIRRORED_RELEASE_IMAGE flapping issue where the SeekOverride function was performing real-time availability checks on each call, leading to inconsistent mirror selection between deployments. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

…ble flapping Remove the MIRRORED_RELEASE_IMAGE environment variable from the ignition-server deployment. This env var was set at deploy-time via SeekOverride, which performs live registry connectivity checks with 15-second timeouts. Network conditions caused it to return different mirror URLs on each reconciliation, triggering non-deterministic deployment updates and pod restarts. MIRRORED_RELEASE_IMAGE is not consumed at runtime by the ignition-server binary. Mirror resolution is already handled through a separate mechanism: ReleaseProvider.Lookup() uses OPENSHIFT_IMG_OVERRIDES at runtime with automatic fallback to the original registry when mirrors are unavailable. The release image for ignition payloads is delivered through token secrets (nodePool.Spec.Release.Image), not through deployment environment variables. Fixes: OCPBUGS-60185 Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com> Commit-Message-Assisted-by: Claude (via Claude Code) Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

…tation Remove the getRegistryOverrides() function which performed live HTTP registry connectivity checks (via LookupMappedImage/GetMetadata) during every CPO reconciliation cycle. These checks returned non-deterministic results depending on network conditions, causing the --registry-overrides container argument to change between reconciliations and triggering unnecessary deployment rollouts and pod restarts. The three per-image overrides computed by getRegistryOverrides() for cluster-config-api, machine-config-operator, and cluster-authentication-operator are redundant: the ignition-server already resolves mirrors at runtime via OPENSHIFT_IMG_OVERRIDES + ImageMetadataProvider.GetOverride()/SeekOverride() in LocalIgnitionProvider.GetPayload(). Additionally, cluster-authentication-operator is not used by the ignition-server at all. Replace with ign.releaseProvider.GetRegistryOverrides() which returns static registry-level overrides from the HostedCluster spec, consistent with how other cpov2 components handle registry overrides. Fixes: OCPBUGS-60185 Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

Adapt the changes from the previous commits (removal of MIRRORED_RELEASE_IMAGE and non-deterministic getRegistryOverrides/ LookupMappedImage logic) to the CPOv1 ignition server reconciliation path. Changes: - Remove MIRRORED_RELEASE_IMAGE env var from reconcileDeployment - Remove mirroredReleaseImage parameter from ReconcileIgnitionServer and reconcileDeployment signatures - Remove LookupMappedImage-based registry override computation that performed live HTTP registry checks causing non-deterministic results - Use static registryOverrides from ReleaseProvider directly - Clean up unused imports (common, registryclient) This ensures functional parity between CPOv1 and CPOv2 for the ignition-server deployment reconciliation. Fixes: OCPBUGS-77367 Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

openshift-ci · 2026-03-06T13:30:31Z

@jparrill: all tests passed!

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.

xiuwang · 2026-03-06T14:13:15Z

/verified by @xiuwang

openshift-ci-robot · 2026-03-06T14:13:28Z

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

Details

In response to this:

/verified by @xiuwang

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.

csrwng · 2026-03-06T14:24:47Z

+
+				// Cache miss - verify mirror availability with 15s timeout
+				verifyCtx, cancel := context.WithTimeout(ctx, 15*time.Second)
+				defer cancel()


nit: it might make sense to make the change from #7846 so we don't keep propagating the bug.

Make sense to me, I will propagate the fix ASAP, but we need this to be in 4.18 also ASAP. So the plan I have in my mind is to push this until 4.18 and then backport the #7846. This is because the customer needs these changes urgently.

csrwng · 2026-03-06T14:27:36Z

/lgtm
/label backport-risk-assessed

jparrill · 2026-03-06T14:33:58Z

/jira refresh

openshift-ci-robot · 2026-03-06T14:34:11Z

@jparrill: This pull request references Jira Issue OCPBUGS-77367, 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.19.z) matches configured target version for branch (4.19.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-77366 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-77366 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
bug has dependents

Requesting review from QA contact:
/cc @xiuwang

This pull request references Jira Issue OCPBUGS-77844, 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.19.z) matches configured target version for branch (4.19.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-65682 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-65682 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
bug has dependents

Requesting review from QA contact:
/cc @xiuwang

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.

openshift-ci-robot · 2026-03-06T14:38:46Z

@jparrill: Jira Issue OCPBUGS-77367: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

openshift/hypershift#7807 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-77367 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Jira Issue Verification Checks: Jira Issue OCPBUGS-77844
✔️ 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-77844 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:

Summary

Manual backport of [release-4.20] OCPBUGS-77366,OCPBUGS-65682: Fix ignition-server pod restarts #7842 to release-4.19

Implements a mirror availability cache with differential TTL to prevent MIRRORED_RELEASE_IMAGE env var flapping that caused massive deployment regeneration

Removes MIRRORED_RELEASE_IMAGE from the ignition-server deployment (dead code not consumed at runtime)

Removes getRegistryOverrides() which performed non-deterministic live HTTP registry checks during every CPO reconciliation, replacing it with static registry-level overrides from the HostedCluster spec

Fixes

OCPBUGS-77367

OCPBUGS-77844

Backport adaptations

The following changes were made beyond the pure cherry-picks to adapt to release-4.19:

support/util/imagemetadata_test.go: Removed unused "fmt" and "os" imports that were residual from the original commit but not referenced in the test code.

control-plane-operator/controllers/hostedcontrolplane/v2/ignitionserver/deployment_test.go: Replaced t.Context() with context.Background() (adding the "context" import), since t.Context() requires Go 1.24 and release-4.19 uses Go 1.23.

All merge conflicts were resolved by accepting the incoming commit version (removal of getRegistryOverrides() and the controller-runtime/pkg/client import).

Test plan

Verify ignition-server deployment no longer sets MIRRORED_RELEASE_IMAGE env var

Verify mirror availability cache works with differential TTL (5min available, 1min unavailable)

Verify deployment remains stable without flapping in disconnected environments

Run unit tests: go test ./support/util/... ./control-plane-operator/controllers/hostedcontrolplane/v2/ignitionserver/...

🤖 Generated with Claude Code

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.

jparrill · 2026-03-06T15:23:42Z

/jira backport release-4.18

openshift-ci-robot · 2026-03-06T15:25:01Z

@jparrill: The following backport issues have been created:

OCPBUGS-77368 for branch release-4.18
OCPBUGS-77923 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.18

Details

In response to this:

/jira backport release-4.18

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 · 2026-03-06T15:26:14Z

@openshift-ci-robot: #7858 failed to apply on top of branch "release-4.18":

Applying: fix: prevent MIRRORED_RELEASE_IMAGE flapping with mirror availability cache
Using index info to reconstruct a base tree...
M	support/util/imagemetadata.go
Falling back to patching base and 3-way merge...
Auto-merging support/util/imagemetadata.go
CONFLICT (content): Merge conflict in support/util/imagemetadata.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 fix: prevent MIRRORED_RELEASE_IMAGE flapping with mirror availability cache

Details

In response to this:

@jparrill: The following backport issues have been created:

OCPBUGS-77368 for branch release-4.18

OCPBUGS-77923 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.18

In response to this:

/jira backport release-4.18

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.

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-merge-robot · 2026-03-07T13:20:06Z

Fix included in accepted release 4.19.0-0.nightly-2026-03-07-080023

jparrill · 2026-03-09T08:22:25Z

/jira refresh

openshift-ci-robot · 2026-03-09T08:22:29Z

@jparrill: Jira Issue OCPBUGS-77367: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

openshift/hypershift#7807 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-77367 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Jira Issue OCPBUGS-77844 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

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.

openshift-ci bot added the do-not-merge/needs-area label Mar 5, 2026

openshift-ci bot requested review from csrwng and sjenning March 5, 2026 10:54

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 6, 2026

jparrill and others added 4 commits March 6, 2026 12:25

jparrill force-pushed the OCPBUGS-77367 branch from 6710ef6 to fe430a4 Compare March 6, 2026 11:35

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

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

csrwng reviewed Mar 6, 2026

View reviewed changes

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 6, 2026

openshift-ci bot assigned csrwng Mar 6, 2026

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 6, 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 Mar 6, 2026

openshift-ci bot requested a review from xiuwang March 6, 2026 14:34

openshift-merge-bot bot merged commit ab16d86 into openshift:release-4.19 Mar 6, 2026
17 checks passed

jparrill mentioned this pull request Mar 6, 2026

[release-4.18] OCPBUGS-77368: Fix ignition-server pod restarts #7878

Merged

Conversation

jparrill commented Mar 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Fixes

Backport adaptations

Test plan

Uh oh!

openshift-ci-robot commented Mar 5, 2026

Summary

Test plan

Uh oh!

coderabbitai bot commented Mar 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

openshift-ci-robot commented Mar 5, 2026

Summary

Test plan

Uh oh!

openshift-ci bot commented Mar 5, 2026

Uh oh!

jparrill commented Mar 5, 2026

Uh oh!

openshift-ci-robot commented Mar 5, 2026

Uh oh!

openshift-ci bot commented Mar 6, 2026

Uh oh!

xiuwang commented Mar 6, 2026

Uh oh!

openshift-ci-robot commented Mar 6, 2026

Uh oh!

csrwng Mar 6, 2026

Choose a reason for hiding this comment

Uh oh!

jparrill Mar 6, 2026

Choose a reason for hiding this comment

Uh oh!

csrwng commented Mar 6, 2026

Uh oh!

jparrill commented Mar 6, 2026

Uh oh!

openshift-ci-robot commented Mar 6, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Mar 6, 2026

Summary

Fixes

Backport adaptations

Test plan

Uh oh!

jparrill commented Mar 6, 2026

Uh oh!

openshift-ci-robot commented Mar 6, 2026

Uh oh!

openshift-cherrypick-robot commented Mar 6, 2026

Uh oh!

openshift-merge-robot commented Mar 7, 2026

Uh oh!

jparrill commented Mar 9, 2026

Uh oh!

openshift-ci-robot commented Mar 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

jparrill commented Mar 5, 2026 •

edited

Loading

coderabbitai bot commented Mar 5, 2026 •

edited

Loading