TRT-2908: Revert openshift/api#2986

[redhat-chai-bot]

Revert

This reverts openshift/api#2986 ("promote OSStreams feature gate to Default for Hypershift") which is breaking 5.0 CI payloads.

Root Cause

PR #2986 enables the MCC OSImageStream discovery code path in proxy-configured HostedClusters. The MCC attempts to reach container registries through a proxy that is unreachable from the management cluster, causing ignition payload generation to fatally error with unable to retrieve any OSImageStream from the configured sources.

Impact

• Failing job:hypershift-e2e-aws — TestCreateClusterProxy fails consistently (2/2 retries)
• Consecutive rejections: 3 (78+ hours without accepted payload in the 5.0 CI stream)
• Last accepted payload:5.0.0-0.ci-2026-08-14-194839
• Only proxy-configured clusters are affected; all other HyperShift tests pass

Tracking

• Jira: TRT-2908
• Related: TRT-2909
• Investigation PR against main: openshift/api#2989

Notes

• 5.1 has the same issue
• This revert unblocks the 5.0 CI stream while the underlying issue is investigated

---

AI-generated. Review for accuracy.

@sosiouxme requested in Slack thread

[openshift-merge-bot]

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]

@redhat-chai-bot: This pull request references TRT-2908 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 bug to target either version "5.0.0." or "openshift-5.0.0.", but it targets "5.1" instead.

Details

In response to this:

Revert

This reverts openshift/api#2986 ("promote OSStreams feature gate to Default for Hypershift") which is breaking 5.0 CI payloads.

Root Cause

PR #2986 enables the MCC OSImageStream discovery code path in proxy-configured HostedClusters. The MCC attempts to reach container registries through a proxy that is unreachable from the management cluster, causing ignition payload generation to fatally error with unable to retrieve any OSImageStream from the configured sources.

Impact

• Failing job:hypershift-e2e-aws — TestCreateClusterProxy fails consistently (2/2 retries)
• Consecutive rejections: 3 (78+ hours without accepted payload in the 5.0 CI stream)
• Last accepted payload:5.0.0-0.ci-2026-08-14-194839
• Only proxy-configured clusters are affected; all other HyperShift tests pass

Tracking

• Jira: TRT-2908
• Related: TRT-2909
• Investigation PR against main: openshift/api#2989

Notes

• 5.1 has the same issue
• This revert unblocks the 5.0 CI stream while the underlying issue is investigated

---

AI-generated. Review for accuracy.

@sosiouxme requested in Slack thread

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]

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

[coderabbitai]

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

Run ID: 9b6aabea-1e12-4e85-b516-696c9cb7e7de

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

---

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

[sosiouxme]

/payload-job periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-ovn

[openshift-ci]

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

• periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c91c5710-9b51-11f1-88e3-69719a3597de-0

[sosiouxme]

/lgtm
but we're back to this again, what the heck?

operator "cluster-capi-operator" contained an invalid image-references file: no input image tag named "aws-cluster-api-controllers"

I thought we were done with this, what is even going on? Let's try again and see if magic happens

/payload-job periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-ovn
/test images

[openshift-ci]

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

• periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/60e35340-9b6c-11f1-9b82-c3912063a89d-0

[openshift-merge-bot]

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sosiouxme
Once this PR has been reviewed and has the lgtm label, please assign deads2k 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:

• OWNERS

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

[openshift-ci]

@redhat-chai-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-serial-techpreview-1of2	5f60ee4	link	true	/test e2e-aws-serial-techpreview-1of2
ci/prow/e2e-aws-serial-1of2	5f60ee4	link	true	/test e2e-aws-serial-1of2
ci/prow/e2e-azure	5f60ee4	link	true	/test e2e-azure
ci/prow/e2e-aws-serial-techpreview-2of2	5f60ee4	link	true	/test e2e-aws-serial-techpreview-2of2
ci/prow/e2e-aws-ovn-techpreview	5f60ee4	link	true	/test e2e-aws-ovn-techpreview
ci/prow/e2e-gcp	5f60ee4	link	true	/test e2e-gcp
ci/prow/images	5f60ee4	link	true	/test images
ci/prow/e2e-upgrade	5f60ee4	link	true	/test e2e-upgrade
ci/prow/e2e-upgrade-out-of-change	5f60ee4	link	true	/test e2e-upgrade-out-of-change
ci/prow/e2e-aws-ovn	5f60ee4	link	true	/test e2e-aws-ovn
ci/prow/e2e-aws-serial-2of2	5f60ee4	link	true	/test e2e-aws-serial-2of2
ci/prow/e2e-aws-ovn-hypershift-conformance	5f60ee4	link	true	/test e2e-aws-ovn-hypershift-conformance
ci/prow/e2e-aws-ovn-hypershift	5f60ee4	link	true	/test e2e-aws-ovn-hypershift

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.