Skip to content

CNTRLPLANE-3874,CNTRLPLANE-3873,OCPBUGS-94518: update azure CPO overrides for 4.20, 4.21, 4.22 - #9211

Merged
celebdor merged 2 commits into
openshift:mainfrom
celebdor:cpo-overrides-cntrlplane-3874-3873-ocpbugs-94518
Aug 7, 2026
Merged

CNTRLPLANE-3874,CNTRLPLANE-3873,OCPBUGS-94518: update azure CPO overrides for 4.20, 4.21, 4.22#9211
celebdor merged 2 commits into
openshift:mainfrom
celebdor:cpo-overrides-cntrlplane-3874-3873-ocpbugs-94518

Conversation

@celebdor

@celebdor celebdor commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

Summary

branch: 4.20 wants: #9055
branch: 4.21 wants: #9054
branch: 4.22 wants: #8865

Test plan

  • go test ./hypershift-operator/controlplaneoperator-overrides/... passes
  • All override images verified pullable via skopeo inspect
  • All claimed PRs verified present in images via verify-pr-in-image.sh
  • New images verified to supersede old images (ancestor check)
  • /validate-pr-override-images passes on this PR

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated Azure control plane operator overrides for OpenShift 4.20, 4.21, and 4.22.
    • Added override coverage through OpenShift 4.22.8.
    • Refreshed image versions and removed overrides that are no longer required.
    • Improved release-version alignment for Azure control plane behavior across supported OpenShift versions.

Update azure CPO image overrides to include recent backports:

- 4.20.0-4.20.32: PR openshift#9055 (cherry-pick to release-4.20)
  Supersedes OCPBUGS-86567 image; extends range from 4.20.24 to 4.20.32.
- 4.21.0-4.21.27: PR openshift#9054 (cherry-pick to release-4.21)
  Supersedes OCPBUGS-86416 image; extends range from 4.21.18 to 4.21.27.
- 4.22.0-4.22.8: PR openshift#8865 (cherry-pick to release-4.22)
  Supersedes CNTRLPLANE-3619/3656/OCPBUGS-98627/98220 image; extends range
  from 4.22.6 to 4.22.8.

All new images are verified to contain the previously overridden fixes.
Next z-streams (4.20.33, 4.21.28, 4.22.9) do not need overrides: all PRs
merged before their development cutoffs (2026-08-05).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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 openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 3, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 3, 2026

Copy link
Copy Markdown

@celebdor: This pull request references CNTRLPLANE-3874 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 task to target either version "5.0." or "openshift-5.0.", but it targets "openshift-4.20.z" instead.

This pull request references CNTRLPLANE-3873 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 task to target either version "5.0." or "openshift-5.0.", but it targets "openshift-4.21.z" instead.

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

  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.22.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, 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.

Details

In response to this:

Summary

branch: 4.20 wants: #9055
branch: 4.21 wants: #9054
branch: 4.22 wants: #8865

Test plan

  • go test ./hypershift-operator/controlplaneoperator-overrides/... passes
  • All override images verified pullable via skopeo inspect
  • All claimed PRs verified present in images via verify-pr-in-image.sh
  • New images verified to supersede old images (ancestor check)
  • /validate-pr-override-images passes on this PR

🤖 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

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: bfddc4d9-943e-46ca-91ca-4e2c25d3f705

📥 Commits

Reviewing files that changed from the base of the PR and between 8e1e07b and d300fda.

📒 Files selected for processing (1)
  • test/e2e/autoscaling_test.go

📝 Walkthrough

Walkthrough

The Azure control plane operator overrides now use updated image digests for OpenShift 4.20, 4.21, and 4.22. The entries cover versions 4.20.0–4.20.32, 4.21.0–4.21.27, and 4.22.0–4.22.8. Comments identify the first versions that no longer require overrides. The paused NodePool autoscaling e2e test now runs only on OpenShift 4.18 or later.

Possibly related PRs

Suggested reviewers: devguyio, jhjaggars

🚥 Pre-merge checks | ✅ 11
✅ Passed checks (11 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly summarizes the main changes: updating Azure CPO overrides for three OpenShift versions.
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 only adds a version guard; all autoscaling subtest titles are static strings, with no dynamic values in test names.
Test Structure And Quality ✅ Passed Test change adds version guard AtLeast(t, Version418) at function start, consistent with codebase patterns. Test has single clear responsibility, proper cleanup via defer, timeouts on cluster opera...
Topology-Aware Scheduling Compatibility ✅ Passed The PR changes only CPO image references in overrides.yaml and adds a version guard in an e2e test; no manifests, controllers, or topology scheduling constraints changed.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The patch adds only an OpenShift version guard to an existing Go e2e subtest; it adds no Ginkgo tests, IPv4 assumptions, or external connectivity.
No-Weak-Crypto ✅ Passed No weak cryptography detected. The PR modifies a YAML config file and adds a version guard to a test file; neither introduces MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto implementations...
Container-Privileges ✅ Passed The PR updates Azure CPO image digests and adds a version guard to skip a test on OpenShift <4.18. No container privilege escalation keywords (privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN,...
No-Sensitive-Data-In-Logs ✅ Passed PR contains only configuration updates and version guards with no logging of sensitive data like passwords, tokens, API keys, PII, or internal hostnames.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@celebdor celebdor added the area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release label Aug 3, 2026
@openshift-ci
openshift-ci Bot requested review from csrwng and devguyio August 3, 2026 18:42
@openshift-ci openshift-ci Bot added the area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release label Aug 3, 2026
@codecov

codecov Bot commented Aug 3, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.96%. Comparing base (5b6a3a7) to head (d300fda).
⚠️ Report is 58 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #9211      +/-   ##
==========================================
+ Coverage   44.94%   44.96%   +0.01%     
==========================================
  Files         778      778              
  Lines       97427    97452      +25     
==========================================
+ Hits        43790    43820      +30     
+ Misses      50616    50607       -9     
- Partials     3021     3025       +4     

see 5 files with indirect coverage changes

Flag Coverage Δ
cmd-support 38.62% <ø> (ø)
cpo-hostedcontrolplane 47.28% <ø> (ø)
cpo-other 45.67% <ø> (ø)
hypershift-operator 55.00% <ø> (+0.07%) ⬆️
other 34.30% <ø> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@celebdor celebdor removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 4, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 4, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aks-4-22
/test e2e-aws-4-22

@openshift-ci

openshift-ci Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: celebdor, csrwng

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:

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

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

machi1990 commented Aug 4, 2026

Copy link
Copy Markdown

/verified by @machi1990

via Azure/ARO-HCP#6395 plus an additional manual verification for the 4.22 ACR pull credentials via managed identity feature similar to #8865 (comment)

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

Copy link
Copy Markdown

@machi1990: This PR has been marked as verified by @machi via https://github.com/Azure/ARO-HCP/pull/6395 plus an additional manual verification for the 4.22 ACR pull credentials via managed identity feature similar to https://github.com/openshift/hypershift/pull/8865#issuecomment-5167125708.

Details

In response to this:

/verified by @machi via Azure/ARO-HCP#6395 plus an additional manual verification for the 4.22 ACR pull credentials via managed identity feature similar to #8865 (comment)

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.

@machi1990

Copy link
Copy Markdown

/verified by @machi1990

@openshift-ci-robot

Copy link
Copy Markdown

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

Details

In response to this:

/verified by @machi1990

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.

@machi1990

Copy link
Copy Markdown

/retest-required

@machi1990

Copy link
Copy Markdown

/retest-required

@openshift-merge-robot

Copy link
Copy Markdown
Contributor

Fix included in release 4.22.0-0.nightly-2026-08-05-022950

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 8c9a9b9 and 2 for PR HEAD 8e1e07b in total

@devguyio

devguyio commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

CI Failure Analysis for PR #9211

All three failing jobs are unrelated to this PR (Azure CPO overrides only — no code changes).

1. e2e-aks-4-22 — ingress operator canary certificate race (3/3 failures)

Root cause: Known bug OCPBUGS-101783 — the canary_certificate_controller in cluster-ingress-operator misses its initial reconciliation due to a startup predicate race. The canary-serving-cert secret is never created, all canary DaemonSet pods stay ContainerCreating (FailedMount), ingress degrades, ClusterVersionAvailable=False.

2. e2e-aws-4-22 — snapshot-controller transient restart (1 failure)

Root cause: csi-snapshot-controller in the TestNodePoolAutoscalingScaleFromZero cluster had restartCount=1. Single container restart on a freshly provisioned scale-from-zero node. The cluster was fully healthy (rollout complete, all conditions valid). All other 17 tests passed EnsureNoCrashingPods.

  • Action: Flake — /retest should pass.

3. e2e-aws-override — missing version guard on TestAutoscalerRespectsNodePoolPause (3/3 failures)

Root cause: The test sets spec.autoscaling.scaleDown (CNTRLPLANE-952, landed in 4.18+) and waits for the CPO to reconcile --scale-down-unneeded-time=60s onto the autoscaler deployment. The e2e-aws-override job creates hosted clusters with 4.17.43 (the latest AWS override version per overrides.yaml testing.latest). The 4.17 CPO predates the entire ScaleUpAndScaleDown / ScaleDown feature — the CPOv2 autoscaler component doesn't even exist on release-4.17.

(Generated by Claude Code, reviewed by @devguyio)

The test sets spec.autoscaling.scaleDown on the HostedCluster and waits
for the CPO to reconcile --scale-down-* args onto the cluster-autoscaler
deployment. This feature was added in CNTRLPLANE-952 and is not present
in the CPO for releases older than 4.18.

The e2e-aws-override job creates clusters with 4.17.43 (the latest AWS
override version), causing 3/3 consistent failures because the 4.17 CPO
has no knowledge of ScaleUpAndScaleDown or ScaleDown args.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com>
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Aug 5, 2026
@openshift-ci openshift-ci Bot added area/testing Indicates the PR includes changes for e2e testing and removed lgtm Indicates that a PR is ready to be merged. labels Aug 5, 2026
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 5, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 5, 2026

Copy link
Copy Markdown

@celebdor: This pull request references CNTRLPLANE-3874 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 task to target either version "5.0." or "openshift-5.0.", but it targets "openshift-4.20.z" instead.

This pull request references CNTRLPLANE-3873 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 task to target either version "5.0." or "openshift-5.0.", but it targets "openshift-4.21.z" instead.

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

  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.22.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified 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:

Summary

branch: 4.20 wants: #9055
branch: 4.21 wants: #9054
branch: 4.22 wants: #8865

Test plan

  • go test ./hypershift-operator/controlplaneoperator-overrides/... passes
  • All override images verified pullable via skopeo inspect
  • All claimed PRs verified present in images via verify-pr-in-image.sh
  • New images verified to supersede old images (ancestor check)
  • /validate-pr-override-images passes on this PR

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
  • Updated Azure control plane operator overrides for OpenShift 4.20, 4.21, and 4.22.
  • Added override coverage through OpenShift 4.22.8.
  • Refreshed image versions and removed overrides that are no longer required.
  • Improved release-version alignment for Azure control plane behavior across supported OpenShift versions.

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.

@machi1990

Copy link
Copy Markdown

/verified by @machi1990

Re-adding the verified label since the newer changes are only on the unit test

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

Copy link
Copy Markdown

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

Details

In response to this:

/verified by @machi1990

Re-adding the verified label since the newer changes are only on the unit test

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.

@devguyio

devguyio commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

/lgtm

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

Copy link
Copy Markdown
Contributor

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

@devguyio

devguyio commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

/test e2e-aks-override

4. e2e-aks-override - TestAdditionalTrustBundlePropagationTest timeout due to client rate limiting (1/3 failures)

Root cause: The test updates spec.additionalTrustBundle on the HostedCluster and polls for UpdatingConfig=True on the NodePool with a 5-minute timeout and 15-second interval. The management cluster client (test/e2e/util/client.go:22-23) is configured with QPS=200, Burst=300, shared across 20 parallel tests. Under peak load, the client-side rate limiter queue saturates and poll requests block until the context deadline expires: client rate limiter Wait returned an error: context deadline exceeded.

The config change did propagate: the machine node-pool-24r2x-test-additional-trust-bundle-propagation-pkgvgf was actively draining at 16:26:21Z, and the NodePool reached correct status 2 minutes after the test timed out. The test just couldn't observe the UpdatingConfig=True transition through the rate limiter backpressure.

(Generated by Claude Code, reviewed by @devguyio)

@cwbotbot

cwbotbot commented Aug 5, 2026

Copy link
Copy Markdown

Test Results

e2e-aws

@devguyio

devguyio commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

5. e2e-kubevirt-aws-ovn-reduced - EnsureCustomLabels/EnsureCustomTolerations fail on CDI importer pod (1/1 runs)

Root cause: The tests check that all pods in the HCP namespace carry hypershift-e2e-test-label=test and the custom toleration. A transient CDI importer-prime-* pod was present during the check. This pod is created by the CDI controller (containerized-data-importer/pkg/controller/import-controller.go:1005-1020) with three hardcoded labels (app=containerized-data-importer, cdi.kubevirt.io, prometheus.cdi.kubevirt.io) and no mechanism to inject external labels.

HyperShift's custom labels are injected by the CPOv2 framework at support/controlplane-component/defaults.go:222 via maps.Copy(podTemplate.Labels, hcp.Spec.Labels), which only runs for CPOv2-managed workloads. CDI is an external operator, not a CPOv2 component, so its pods never go through this path.

The existing KubeVirt skip list (test/e2e/util/util.go:3497) only covers virt-launcher and vmi-console-debug pods (added in e65f17c682). The CDI importer-prime-* pod is a different category that was not accounted for. It's transient (exists only during disk image import), so the test only fails when the label check coincides with an active import.

EnsureAppLabel passed because the pod does have an app label (containerized-data-importer), confirming the pod was present for both checks.

Not related to PR #9211.

(Generated by Claude Code, reviewed by @devguyio)

@devguyio

devguyio commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

/test e2e-aws

6. e2e-aws - TestKarpenterUpgradeControlPlane context canceled after successful upgrade (1/1 runs)

Root cause: The control plane upgrade completed successfully (rollout in 18m30s), drift validation passed, but at karpenter_control_plane_upgrade_test.go:93 a trivial mgtClient.Get() to refresh the HostedCluster object failed with client rate limiter Wait returned an error: context canceled. The test's parent context had already expired after 2855s (~47 min) of total test time. Same root cause as the e2e-aks-override failure: the management client (test/e2e/util/client.go:22-23, QPS=200, Burst=300) was saturated by 20 parallel tests.

607/610 tests passed. Not related to PR #9211.

(Generated by Claude Code, reviewed by @devguyio)

@devguyio

devguyio commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

/test e2e-v2-gke

7. e2e-v2-gke - csi-snapshot-controller restart during startup (1/1 runs)

Root cause: The snapshot-controller container exited with code 1 on first start because it couldn't verify VolumeSnapshot CRDs exist. From the pod's lastState.terminated.message:

Failed to list v1 volumesnapshots: Get "https://kube-apiserver:6443/apis/snapshot.storage.k8s.io/v1/volumesnapshots?limit=1": context deadline exceeded
Exiting due to failure to ensure CRDs exist during startup: context deadline exceeded

The controller has a 30-second internal timeout for this CRD check (startedAt: 17:48:59, finishedAt: 17:49:29). The kube-apiserver wasn't fully ready to serve the snapshot.storage.k8s.io/v1 API group in that window. On restart, the apiserver was ready and the controller came up normally. 399/400 tests passed.

Not related to PR #9211.

(Generated by Claude Code, reviewed by @devguyio)

@celebdor celebdor 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 7, 2026
@celebdor

celebdor commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator Author

/override "ci/prow/e2e-kubevirt-aws-ovn-reduced"

@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@celebdor: Overrode contexts on behalf of celebdor: ci/prow/e2e-kubevirt-aws-ovn-reduced

Details

In response to this:

/override "ci/prow/e2e-kubevirt-aws-ovn-reduced"

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.

@celebdor

celebdor commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator Author

/override "ci/prow/verify"
/override "ci/prow/unit"

@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@celebdor: Overrode contexts on behalf of celebdor: ci/prow/unit, ci/prow/verify

Details

In response to this:

/override "ci/prow/verify"
/override "ci/prow/unit"

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.

@celebdor
celebdor merged commit 0caf220 into openshift:main Aug 7, 2026
43 of 46 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

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

Details

In response to this:

Summary

branch: 4.20 wants: #9055
branch: 4.21 wants: #9054
branch: 4.22 wants: #8865

Test plan

  • go test ./hypershift-operator/controlplaneoperator-overrides/... passes
  • All override images verified pullable via skopeo inspect
  • All claimed PRs verified present in images via verify-pr-in-image.sh
  • New images verified to supersede old images (ancestor check)
  • /validate-pr-override-images passes on this PR

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
  • Updated Azure control plane operator overrides for OpenShift 4.20, 4.21, and 4.22.
  • Added override coverage through OpenShift 4.22.8.
  • Refreshed image versions and removed overrides that are no longer required.
  • Improved release-version alignment for Azure control plane behavior across supported OpenShift versions.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release area/testing Indicates the PR includes changes for e2e testing jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants