ci: bump hypershift nested management cluster to 5.0.0 nightly

[redhat-chai-bot]

Summary

Bump the default HYPERSHIFT_HC_RELEASE_IMAGE for the nested management cluster
from 4.22.0-ec.5-multi to 5.0.0-0.nightly-2026-08-14-034145-multi.

Why

The e2e-v2-azure-self-managed job has been persistently failing because the
management cluster uses 4.22.0-ec.5-multi, which includes the now-removed
redhat-marketplace OLM catalog source. The catalog is no longer available,
causing the management cluster to never reach Available.

The fix to remove the catalog dependency from HyperShift landed in
openshift/hypershift#8958 (merged Aug 12). The
5.0.0-ec.6 image predates that merge, so we use the Aug 14 nightly which
includes the fix.

A backport to release-4.22 is in progress at
openshift/hypershift#9289.

What changed

ci-operator/step-registry/hypershift/setup-nested-management-cluster/hypershift-setup-nested-management-cluster-chain.yaml

-ocp-release:4.22.0-ec.5-multi
+ocp-release:5.0.0-0.nightly-2026-08-14-034145-multi

---

AI-generated. Review for accuracy.

@csrwng requested in Slack thread

Summary by CodeRabbit

• Updates the default HyperShift release image for the nested management cluster to a 5.0.0 nightly build.
• Fixes persistent e2e-v2-azure-self-managed failures caused by the removed redhat-marketplace OLM catalog source.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: redhat-chai-bot
Once this PR has been reviewed and has the lgtm label, please assign csrwng for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• ci-operator/step-registry/hypershift/OWNERS

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

[coderabbitai]

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

Run ID: 28203047-fe0d-41f0-8cc9-67a39f1231ec

📥 Commits

Reviewing files that changed from the base of the PR and between b826a6e and 128ba61.

📒 Files selected for processing (1)

• ci-operator/step-registry/hypershift/setup-nested-management-cluster/hypershift-setup-nested-management-cluster-chain.yaml

---

Walkthrough

The nested HyperShift management cluster setup now uses the specified 5.0 nightly hosted-cluster release image by default.

Changes

HyperShift release image

Layer / File(s)	Summary
Update default release image ci-operator/step-registry/hypershift/setup-nested-management-cluster/hypershift-setup-nested-management-cluster-chain.yaml	Updates HYPERSHIFT_HC_RELEASE_IMAGE from the 4.22 release image to the specified 5.0 nightly release image.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: 🔵 Low · up to 128ba

The PR updates the nested management cluster to a specific nightly release image; if that image is unavailable, inaccessible, or not multi-architecture, cluster setup can fail before testing begins. The change is otherwise mergeable with explicit owner verification of the image.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the CI change: updating the HyperShift nested management cluster to a 5.0.0 nightly release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The diff changes only a default release-image value in YAML. No Ginkgo test-title construct or test file changed, so no unstable test name was introduced.
Test Structure And Quality	✅ Passed	The patch changes one YAML release-image default only. It adds no Ginkgo test code, so the listed test-quality requirements do not apply.
Microshift Test Compatibility	✅ Passed	The commit changes only one YAML release-image default and adds no Ginkgo tests or test files, so MicroShift test compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR changes only one YAML default release image; the parent diff adds no Ginkgo tests or test code, so SNO test compatibility does not apply.
Topology-Aware Scheduling Compatibility	✅ Passed	The diff changes only the HyperShift release-image string. It adds no deployment scheduling constraints, replica logic, affinity, selectors, tolerations, or PDB settings.
Ote Binary Stdout Contract	✅ Passed	The PR changes one release-image value in a YAML chain; it does not change an OTE binary or process-level stdout behavior.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The diff changes only one YAML release-image value; it adds no Ginkgo e2e tests or new IPv4 or external-connectivity behavior.
No-Weak-Crypto	✅ Passed	The commit changes only the default release-image string; added-line scanning found no flagged algorithms, crypto implementation, or secret comparison. Existing sha256sum use is unchanged.
Container-Privileges	✅ Passed	The commit changes only the default release-image string; the YAML contains no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The parent diff changes only the default public release-image reference; it adds no logging and exposes no password, token, API key, PII, hostname, or customer data.

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@redhat-chai-bot: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-openstack-resource-controller-main-e2e-hypershift	openshift/openstack-resource-controller	presubmit	Registry content changed
pull-ci-openshift-openstack-resource-controller-release-5.1-e2e-hypershift	openshift/openstack-resource-controller	presubmit	Registry content changed
pull-ci-openshift-openstack-resource-controller-release-5.0-e2e-hypershift	openshift/openstack-resource-controller	presubmit	Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.23-e2e-hypershift	openshift/openstack-resource-controller	presubmit	Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.22-e2e-hypershift	openshift/openstack-resource-controller	presubmit	Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.21-e2e-hypershift	openshift/openstack-resource-controller	presubmit	Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.20-e2e-hypershift	openshift/openstack-resource-controller	presubmit	Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.19-e2e-hypershift	openshift/openstack-resource-controller	presubmit	Registry content changed
pull-ci-openshift-csi-operator-main-hypershift-e2e-openstack-aws-csi-cinder	openshift/csi-operator	presubmit	Registry content changed
pull-ci-openshift-csi-operator-main-hypershift-e2e-openstack-aws-csi-manila	openshift/csi-operator	presubmit	Registry content changed
pull-ci-openshift-csi-operator-release-5.1-hypershift-e2e-openstack-aws-csi-cinder	openshift/csi-operator	presubmit	Registry content changed
pull-ci-openshift-csi-operator-release-5.1-hypershift-e2e-openstack-aws-csi-manila	openshift/csi-operator	presubmit	Registry content changed
pull-ci-openshift-csi-operator-release-5.0-hypershift-e2e-openstack-aws-csi-cinder	openshift/csi-operator	presubmit	Registry content changed
pull-ci-openshift-csi-operator-release-5.0-hypershift-e2e-openstack-aws-csi-manila	openshift/csi-operator	presubmit	Registry content changed
pull-ci-openshift-csi-operator-release-4.23-hypershift-e2e-openstack-aws-csi-cinder	openshift/csi-operator	presubmit	Registry content changed
pull-ci-openshift-csi-operator-release-4.23-hypershift-e2e-openstack-aws-csi-manila	openshift/csi-operator	presubmit	Registry content changed
pull-ci-openshift-cluster-storage-operator-main-hypershift-e2e-openstack-aws-csi-cinder	openshift/cluster-storage-operator	presubmit	Registry content changed
pull-ci-openshift-cluster-storage-operator-main-hypershift-e2e-openstack-aws-csi-manila	openshift/cluster-storage-operator	presubmit	Registry content changed
pull-ci-openshift-cluster-storage-operator-release-5.1-hypershift-e2e-openstack-aws-csi-cinder	openshift/cluster-storage-operator	presubmit	Registry content changed
pull-ci-openshift-cluster-storage-operator-release-5.1-hypershift-e2e-openstack-aws-csi-manila	openshift/cluster-storage-operator	presubmit	Registry content changed
pull-ci-openshift-cluster-storage-operator-release-5.0-hypershift-e2e-openstack-aws-csi-cinder	openshift/cluster-storage-operator	presubmit	Registry content changed
pull-ci-openshift-cluster-storage-operator-release-5.0-hypershift-e2e-openstack-aws-csi-manila	openshift/cluster-storage-operator	presubmit	Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.23-hypershift-e2e-openstack-aws-csi-cinder	openshift/cluster-storage-operator	presubmit	Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.23-hypershift-e2e-openstack-aws-csi-manila	openshift/cluster-storage-operator	presubmit	Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.22-hypershift-e2e-openstack-aws-csi-cinder	openshift/cluster-storage-operator	presubmit	Registry content changed

A total of 297 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[csrwng]

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-v2-azure-self-managed

[openshift-merge-bot]

@csrwng: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@redhat-chai-bot: 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/rehearse/openshift/hypershift/main/e2e-v2-azure-self-managed	128ba61	link	unknown	/pj-rehearse pull-ci-openshift-hypershift-main-e2e-v2-azure-self-managed

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.