OCPBUGS-94170: fix registry override matching and propagation to init containers by avollmer-redhat · Pull Request #8877 · openshift/hypershift

avollmer-redhat · 2026-06-30T16:07:22Z

Summary

Combined manual backport of #8509 and #8824 to release-4.22.

The cherry-pick bot could not create this backport automatically because the support/util/registryoverride/ package does not exist on release-4.22 (it was introduced on main by #8509), causing merge conflicts.

What this fixes

Registry override substring matching bug (OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509): RegistryMirrorProviderDecorator.Lookup() used strings.Replace which could match substrings inside hostnames (e.g. quay.io inside quay.io.example.com). Replaced with strict longest-prefix matching via new registryoverride.Replace() helper.
Digest/tag separator handling (OCPBUGS-92034: fix registry override matching for digest and tag separators #8824): The strict matching from OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509 only accepted / as a valid separator. Repository-level overrides failed to match digest-based references (repo@sha256:...). Fixed matchesPrefix() to also accept @ (digest) and : (tag, when source contains a path component).
Init container image override propagation (OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509): CPO-managed init containers (e.g. availability-prober) were not getting registry overrides applied because imageprovider.New() populated component images without running them through override logic. Added NewWithRegistryOverrides() and wired it into the HCP controller.

Root cause

Without these fixes, ValidatingAdmissionPolicies in Deny mode block HCP creation because CPO init containers still reference original registries (e.g. quay.io/redhat-user-workloads/...) instead of the configured mirror/ACR.

Changes

New: support/util/registryoverride/ package with Replace() and comprehensive tests (18 test cases)
Modified: support/releaseinfo/registry_mirror_provider.go — use registryoverride.Replace() instead of strings.Replace
Modified: control-plane-operator/.../imageprovider/imageprovider.go — add NewWithRegistryOverrides()
Modified: control-plane-operator/.../hostedcontrolplane_controller.go — wire NewWithRegistryOverrides with registry overrides from the release provider

Test plan

18 unit tests for registryoverride.Replace covering boundary matching, longest-prefix, digest/tag separators, false-positive rejection, mutation safety
All existing releaseinfo tests pass
All existing imageprovider tests pass (compilation verified)

Upstream PRs: OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509, OCPBUGS-92034: fix registry override matching for digest and tag separators #8824
Jira: OCPBUGS-94170, OCPBUGS-85585, OCPBUGS-92034
Requested by @muraee in [release-4.22] OCPBUGS-94170: tighten registry override matching to strict longest-prefix across release-image consumers #8873 (closed, asked for combined backport including OCPBUGS-92034: fix registry override matching for digest and tag separators #8824)

/cc @muraee @sjenning @raelga

openshift-merge-bot · 2026-06-30T16:07:25Z

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-06-30T16:07:29Z

@avollmer-redhat: This pull request references Jira Issue OCPBUGS-94170, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.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-85585 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-85585 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
bug has dependents

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

Combined manual backport of #8509 and #8824 to release-4.22.

The cherry-pick bot could not create this backport automatically because the support/util/registryoverride/ package does not exist on release-4.22 (it was introduced on main by #8509), causing merge conflicts.

What this fixes

Registry override substring matching bug (OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509): RegistryMirrorProviderDecorator.Lookup() used strings.Replace which could match substrings inside hostnames (e.g. quay.io inside quay.io.example.com). Replaced with strict longest-prefix matching via new registryoverride.Replace() helper.

Digest/tag separator handling (OCPBUGS-92034: fix registry override matching for digest and tag separators #8824): The strict matching from OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509 only accepted / as a valid separator. Repository-level overrides failed to match digest-based references (repo@sha256:...). Fixed matchesPrefix() to also accept @ (digest) and : (tag, when source contains a path component).

Init container image override propagation (OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509): CPO-managed init containers (e.g. availability-prober) were not getting registry overrides applied because imageprovider.New() populated component images without running them through override logic. Added NewWithRegistryOverrides() and wired it into the HCP controller.

Root cause

Without these fixes, ValidatingAdmissionPolicies in Deny mode block HCP creation because CPO init containers still reference original registries (e.g. quay.io/redhat-user-workloads/...) instead of the configured mirror/ACR.

Changes

New: support/util/registryoverride/ package with Replace() and comprehensive tests (18 test cases)

Modified: support/releaseinfo/registry_mirror_provider.go — use registryoverride.Replace() instead of strings.Replace

Modified: control-plane-operator/.../imageprovider/imageprovider.go — add NewWithRegistryOverrides()

Modified: control-plane-operator/.../hostedcontrolplane_controller.go — wire NewWithRegistryOverrides with registry overrides from the release provider

Test plan

18 unit tests for registryoverride.Replace covering boundary matching, longest-prefix, digest/tag separators, false-positive rejection, mutation safety

All existing releaseinfo tests pass

All existing imageprovider tests pass (compilation verified)

Related

Upstream PRs: OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509, OCPBUGS-92034: fix registry override matching for digest and tag separators #8824

Jira: OCPBUGS-94170, OCPBUGS-85585, OCPBUGS-92034

Requested by @muraee in [release-4.22] OCPBUGS-94170: tighten registry override matching to strict longest-prefix across release-image consumers #8873 (closed, asked for combined backport including OCPBUGS-92034: fix registry override matching for digest and tag separators #8824)

/cc @muraee @sjenning @raelga

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-06-30T16:07:31Z

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 YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: e381aeac-69fa-403d-bf3a-d9a64d97ff5a

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

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.}

avollmer-redhat · 2026-06-30T16:07:38Z

/label backport-risk-assessed

This is a combined manual backport of #8509 + #8824 as requested by @muraee in #8873.

Backport risk assessment: Low risk. The changes add a new leaf package (registryoverride) with no internal dependencies, fix a strings.Replace call to use strict prefix matching, and wire registry overrides into the image provider for init containers. All changes are additive — no existing behavior changes unless --registry-overrides is configured, and when it is, the fix ensures overrides are correctly applied to all images rather than using the broken substring matching.

openshift-ci · 2026-06-30T16:09:12Z

@avollmer-redhat: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-staff-engineers, openshift-release-oversight, openshift-sustaining-engineers

Details

In response to this:

/label backport-risk-assessed

This is a combined manual backport of #8509 + #8824 as requested by @muraee in #8873.

Backport risk assessment: Low risk. The changes add a new leaf package (registryoverride) with no internal dependencies, fix a strings.Replace call to use strict prefix matching, and wire registry overrides into the image provider for init containers. All changes are additive — no existing behavior changes unless --registry-overrides is configured, and when it is, the fix ensures overrides are correctly applied to all images rather than using the broken substring matching.

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.

muraee · 2026-06-30T16:10:29Z

/approve

codecov · 2026-06-30T22:12:44Z

Codecov Report

❌ Patch coverage is 70.73171% with 12 lines in your changes missing coverage. Please review.
✅ Project coverage is 35.87%. Comparing base (5cb8735) to head (714067c).
⚠️ Report is 50 commits behind head on release-4.22.

Files with missing lines	Patch %	Lines
.../hostedcontrolplane/imageprovider/imageprovider.go	0.00%	11 Missing ⚠️
support/releaseinfo/registry_mirror_provider.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@               Coverage Diff                @@
##           release-4.22    #8877      +/-   ##
================================================
+ Coverage         35.45%   35.87%   +0.42%     
================================================
  Files               767      775       +8     
  Lines             93724    94768    +1044     
================================================
+ Hits              33226    33996     +770     
- Misses            57785    57991     +206     
- Partials           2713     2781      +68

Files with missing lines	Coverage Δ
...ostedcontrolplane/hostedcontrolplane_controller.go	`36.78% <ø> (+0.02%)`	⬆️
support/util/registryoverride/registryoverride.go	`100.00% <100.00%> (ø)`
support/releaseinfo/registry_mirror_provider.go	`45.45% <0.00%> (+1.97%)`	⬆️
.../hostedcontrolplane/imageprovider/imageprovider.go	`60.00% <0.00%> (-15.00%)`	⬇️

... and 31 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

…t containers Combined manual backport of openshift#8509 and openshift#8824 to release-4.22. Introduces strict longest-prefix registry override matching and wires overrides into CPO init container image resolution.

raelga

Cherry picks two already tested and shiped changes.

/lgtm

openshift-ci · 2026-07-02T14:24:42Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avollmer-redhat, muraee, raelga

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

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

openshift-merge-bot · 2026-07-02T14:24:42Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aks
/test e2e-aws
/test e2e-aws-upgrade-hypershift-operator
/test e2e-azure-self-managed
/test e2e-kubevirt-aws-ovn-reduced
/test e2e-v2-aws

raelga · 2026-07-02T14:41:20Z

/retest

avollmer-redhat · 2026-07-02T16:27:06Z

/retest

raelga · 2026-07-03T10:43:47Z

/retest

avollmer-redhat · 2026-07-06T17:45:02Z

/retest-required

Newer 4.19 CI payloads are now available (Jul 4, Jul 6) — the previous e2e-aws and e2e-aks failures were caused by a missing baremetal-installer image in the stale 4.19.0-0.ci-2026-06-25-212724 payload.

avollmer-redhat · 2026-07-07T05:22:48Z

CI blocker update — 4.19 CI stream deadlocked, escalated to `#forum-ocp-testplatform`

Root cause identified

The 4.19 CI candidate resolver is stuck on payload 4.19.0-0.ci-2026-06-25-212724, which has a missing baremetal-installer image (sha256:c4bc76eeaec462f86a2134bcccdf6558f1865f15b87754dbab018a2ea842d0ee). No newer 4.19 CI payload has been accepted since Jun 25 — every subsequent payload (Jul 4, Jul 6) has been Rejected.

The deadlock

The 4.19 CI stream is stuck in a circular failure loop. The blocking verification jobs for new payloads (e.g. hypershift-e2e-aws, hypershift-e2e-aks, upgrade jobs) use the release:initial step, which imports the last accepted 4.19 payload — the broken Jun 25 one. Since that payload has a missing image, the verification jobs fail, the new payload gets rejected, and the resolver stays pinned to the broken Jun 25 payload. No new 4.19 CI payload can ever pass verification until this cycle is broken.

Confirmed by checking the Jul 6 payload verification logs: the error is [release:initial] failed: failed to import release 4.19.0-0.ci-2026-06-25-212724 — even though this is supposed to be verifying the Jul 6 payload.

Escalation

Posted to #forum-ocp-testplatform and tagged @dptp-triage. Requested either a force-accept of a newer payload or republication of the missing image.

Impact on this PR

e2e-aws and e2e-aks will continue failing with the same baremetal-installer not found error on every retest until DPTP/TRT resolves the 4.19 CI stream deadlock.
All other jobs pass (verify-deps, security, images, e2e-azure-self-managed, e2e-kubevirt-aws-ovn-reduced, e2e-v2-aws, e2e-aws-upgrade-hypershift-operator).
This is a CI infrastructure issue affecting all HyperShift backport PRs referencing 4.19 (see also [release-4.22] CNTRLPLANE-3884: Add spec.monitoring API for metrics forwarding #8872, [release-4.21] OCPBUGS-94179: fix registry override matching and propagation to init containers #8879, [release-4.20] OCPBUGS-94180: fix registry override matching and propagation to init containers #8880).

Will retest once the 4.19 CI stream is unblocked.

avollmer-redhat · 2026-07-08T14:46:04Z

/retest-required

raelga · 2026-07-13T08:07:21Z

/retest-required

avollmer-redhat · 2026-07-13T19:23:17Z

/retest ci/prow/e2e-aws

avollmer-redhat · 2026-07-13T22:49:16Z

/retest ci/prow/e2e-aws

avollmer-redhat · 2026-07-13T23:37:28Z

The e2e-aws failure (Services is immutable, ControllerAvailabilityPolicy is immutable, Capabilities is immutable) is a pre-existing test issue on release-4.22, confirmed by the periodic job:

Periodic job: periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn
Build: 2074836880272134144 (Jul 8, no PR code)
Same errors at lines 1276-1279 and 3656-3659 of the nested e2e build log

This is unrelated to the registry override changes in this PR.

/retest ci/prow/e2e-aws

avollmer-redhat · 2026-07-13T23:42:27Z

/test e2e-aws

avollmer-redhat · 2026-07-14T17:05:53Z

@sjenning @muraee All CI is now green (10/10 jobs passing, including e2e-aws and e2e-aks). Could one of you apply the remaining labels needed to merge?

/label backport-risk-assessed
/label verified

This is blocking the 4.21 and 4.20 backports (#8879, #8880) which depend on this merging first via the Jira dependency chain.

openshift-ci · 2026-07-14T17:06:24Z

@avollmer-redhat: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-staff-engineers, openshift-release-oversight, openshift-sustaining-engineers

Details

In response to this:

@sjenning @muraee All CI is now green (10/10 jobs passing, including e2e-aws and e2e-aks). Could one of you apply the remaining labels needed to merge?
/label backport-risk-assessed
/label verified
This is blocking the 4.21 and 4.20 backports (#8879, #8880) which depend on this merging first via the Jira dependency chain.

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.

avollmer-redhat · 2026-07-16T19:58:47Z

@sjenning @muraee Friendly follow-up — this PR is one label away from merging. All 10/10 CI jobs are green, and verified was added (thank you). Just need:

/label backport-risk-assessed

This is the gate for the 4.21 and 4.20 backports (#8879, #8880) which can't merge until this one lands. Tracked under OCPBUGS-94170 / ARO-22152 (FSI image sourcing compliance).

openshift-ci · 2026-07-16T19:59:15Z

@avollmer-redhat: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-staff-engineers, openshift-release-oversight, openshift-sustaining-engineers

Details

In response to this:

@sjenning @muraee Friendly follow-up — this PR is one label away from merging. All 10/10 CI jobs are green, and verified was added (thank you). Just need:
/label backport-risk-assessed
This is the gate for the 4.21 and 4.20 backports (#8879, #8880) which can't merge until this one lands. Tracked under OCPBUGS-94170 / ARO-22152 (FSI image sourcing compliance).

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.

avollmer-redhat · 2026-07-30T17:05:10Z

@CEWong can you add the backport-risk-assessed label to this PR?

openshift-ci · 2026-08-03T09:18:39Z

@avollmer-redhat: 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.

openshift-ci-robot · 2026-08-03T09:22:49Z

@avollmer-redhat: Jira Issue OCPBUGS-94170: Some pull requests linked via external trackers have merged:

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

openshift/hypershift#8873 is closed

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-94170 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.

Details

In response to this:

Summary

Combined manual backport of #8509 and #8824 to release-4.22.

The cherry-pick bot could not create this backport automatically because the support/util/registryoverride/ package does not exist on release-4.22 (it was introduced on main by #8509), causing merge conflicts.

What this fixes

Registry override substring matching bug (OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509): RegistryMirrorProviderDecorator.Lookup() used strings.Replace which could match substrings inside hostnames (e.g. quay.io inside quay.io.example.com). Replaced with strict longest-prefix matching via new registryoverride.Replace() helper.

Digest/tag separator handling (OCPBUGS-92034: fix registry override matching for digest and tag separators #8824): The strict matching from OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509 only accepted / as a valid separator. Repository-level overrides failed to match digest-based references (repo@sha256:...). Fixed matchesPrefix() to also accept @ (digest) and : (tag, when source contains a path component).

Init container image override propagation (OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509): CPO-managed init containers (e.g. availability-prober) were not getting registry overrides applied because imageprovider.New() populated component images without running them through override logic. Added NewWithRegistryOverrides() and wired it into the HCP controller.

Root cause

Without these fixes, ValidatingAdmissionPolicies in Deny mode block HCP creation because CPO init containers still reference original registries (e.g. quay.io/redhat-user-workloads/...) instead of the configured mirror/ACR.

Changes

New: support/util/registryoverride/ package with Replace() and comprehensive tests (18 test cases)

Modified: support/releaseinfo/registry_mirror_provider.go — use registryoverride.Replace() instead of strings.Replace

Modified: control-plane-operator/.../imageprovider/imageprovider.go — add NewWithRegistryOverrides()

Modified: control-plane-operator/.../hostedcontrolplane_controller.go — wire NewWithRegistryOverrides with registry overrides from the release provider

Test plan

18 unit tests for registryoverride.Replace covering boundary matching, longest-prefix, digest/tag separators, false-positive rejection, mutation safety

All existing releaseinfo tests pass

All existing imageprovider tests pass (compilation verified)

Related

Upstream PRs: OCPBUGS-85585: tighten registry override matching to strict longest-prefix across release-image consumers #8509, OCPBUGS-92034: fix registry override matching for digest and tag separators #8824

Jira: OCPBUGS-94170, OCPBUGS-85585, OCPBUGS-92034

Requested by @muraee in [release-4.22] OCPBUGS-94170: tighten registry override matching to strict longest-prefix across release-image consumers #8873 (closed, asked for combined backport including OCPBUGS-92034: fix registry override matching for digest and tag separators #8824)

/cc @muraee @sjenning @raelga

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.

avollmer-redhat · 2026-08-05T14:45:37Z

/jira refresh

openshift-ci-robot · 2026-08-05T14:45:43Z

@avollmer-redhat: Jira Issue OCPBUGS-94170: Some pull requests linked via external trackers have merged:

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

openshift/hypershift#8873 is closed

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-94170 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.

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.

avollmer-redhat · 2026-08-05T15:11:01Z

/jira refresh

openshift-ci-robot · 2026-08-05T15:11:06Z

@avollmer-redhat: Jira Issue Verification Checks: Jira Issue OCPBUGS-94170
✔️ 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-94170 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:

/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 added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jun 30, 2026

openshift-ci Bot requested review from muraee, raelga and sjenning June 30, 2026 16:07

openshift-ci Bot added the do-not-merge/needs-area label Jun 30, 2026

This was referenced Jun 30, 2026

[release-4.21] OCPBUGS-94179: fix registry override matching and propagation to init containers #8879

Merged

[release-4.20] OCPBUGS-94180: fix registry override matching and propagation to init containers #8880

Open

avollmer-redhat force-pushed the fix/OCPBUGS-94170-combined-backport-4.22 branch from d62a7b1 to fb88a55 Compare June 30, 2026 21:57

avollmer-redhat force-pushed the fix/OCPBUGS-94170-combined-backport-4.22 branch from fb88a55 to 5153904 Compare July 1, 2026 15:23

avollmer-redhat force-pushed the fix/OCPBUGS-94170-combined-backport-4.22 branch from 5153904 to 714067c Compare July 1, 2026 16:41

avollmer-redhat mentioned this pull request Jul 1, 2026

[release-4.22] OCPBUGS-94170: tighten registry override matching to strict longest-prefix across release-image consumers #8873

Closed

raelga approved these changes Jul 2, 2026

View reviewed changes

openshift-ci Bot assigned raelga Jul 2, 2026

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

openshift-ci Bot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 14, 2026

csrwng added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 3, 2026

openshift-merge-bot Bot merged commit 11cafa3 into openshift:release-4.22 Aug 3, 2026
24 checks passed

avollmer-redhat mentioned this pull request Aug 11, 2026

Bug 105607: [release-4.19] CPO does not propagate --registry-overrides to init containers it injects in HCP sub-resources #9278

Closed

Uh oh!

Conversation

avollmer-redhat commented Jun 30, 2026

Summary

What this fixes

Root cause

Changes

Test plan

Related

Uh oh!

openshift-merge-bot Bot commented Jun 30, 2026

Uh oh!

openshift-ci-robot commented Jun 30, 2026

Summary

What this fixes

Root cause

Changes

Test plan

Related

Uh oh!

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

Uh oh!

Review skipped

Uh oh!

avollmer-redhat commented Jun 30, 2026

Uh oh!

openshift-ci Bot commented Jun 30, 2026

Uh oh!

muraee commented Jun 30, 2026

Uh oh!

codecov Bot commented Jun 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

raelga left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci Bot commented Jul 2, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 2, 2026

Uh oh!

raelga commented Jul 2, 2026

Uh oh!

avollmer-redhat commented Jul 2, 2026

Uh oh!

raelga commented Jul 3, 2026

Uh oh!

avollmer-redhat commented Jul 6, 2026

Uh oh!

avollmer-redhat commented Jul 7, 2026

CI blocker update — 4.19 CI stream deadlocked, escalated to #forum-ocp-testplatform

Root cause identified

The deadlock

Escalation

Impact on this PR

Uh oh!

avollmer-redhat commented Jul 8, 2026

Uh oh!

raelga commented Jul 13, 2026

Uh oh!

avollmer-redhat commented Jul 13, 2026

Uh oh!

avollmer-redhat commented Jul 13, 2026

Uh oh!

avollmer-redhat commented Jul 13, 2026

Uh oh!

avollmer-redhat commented Jul 13, 2026

Uh oh!

avollmer-redhat commented Jul 14, 2026

Uh oh!

openshift-ci Bot commented Jul 14, 2026

Uh oh!

avollmer-redhat commented Jul 16, 2026 • 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 Jul 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

avollmer-redhat commented Jul 30, 2026

Uh oh!

coderabbitai Bot commented Jun 30, 2026 •

edited

Loading

codecov Bot commented Jun 30, 2026 •

edited

Loading

CI blocker update — 4.19 CI stream deadlocked, escalated to `#forum-ocp-testplatform`

avollmer-redhat commented Jul 16, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci Bot commented Jul 16, 2026 •

edited

Loading