Uh oh!
There was an error while loading. Please reload this page.
Revert "CNTRLPLANE-3871: promote OSStreams feature gate to Default for Hypershift" - #2989
Conversation
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
@redhat-chai-bot: This pull request references CNTRLPLANE-3871 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 story to target either version "5.1.0." or "openshift-5.1.0.", but it targets "openshift-5.0" instead. DetailsIn response to this:
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. |
Hello @redhat-chai-bot! Some important instructions when contributing to openshift/api: |
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (10)
📒 Files selected for processing (12)
💤 Files with no reviewable changes (2)
Included review availability: Your plan includes up to 2 reviews per rolling hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe change updates OSStreams enablement by cluster profile and feature set. It enables SelfManaged variants and selected Hypershift preview variants while disabling Hypershift default and OKD defaults. It adds MachineConfigPool CRDs for multiple Hypershift profiles with validation and status schemas. It also adds the Hypershift OSImageStream CRD with default-stream and image validation rules. Possibly related PRs
Merge Risk:⚪ Minimal · up to The change restores the prior Hypershift OSStreams feature-gate behavior and generated manifests; no actionable merge-blocking risk remains after normal checks. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 golangci-lint (2.12.2)Error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented 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. Comment |
To be clear, this is just a suspect at this point; running the payload job to gather evidence. Also chai is out of line asking whether it's the "root cause". It's certainly not, but perhaps the proximate cause. |
sosiouxme
commented
Aug 18, 2026
/payload-job periodic-ci-openshift-hypershift-release-5.1-periodics-e2e-aws-ovn |
@sosiouxme: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/35f79e20-9b08-11f1-995f-b8fc12949438-0 |
redhat-chai-bot
commented
Aug 18, 2026
/retest verify AI-generated. Review for accuracy. |
sosiouxme
commented
Aug 18, 2026
/test verify |
@redhat-chai-bot: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
neisw
commented
Aug 18, 2026
/lgtm |
Scheduling tests matching the |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: neisw The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
This reverts the merge commit from #2950.
PR #2950 promoted the OSStreams feature gate to Default for Hypershift. It is suspected as a possible contributor to the
TestCreateClusterProxyregression observed in recent5.1.0-0.ciand5.0payload rejections, where worker nodes receive HTTP 407 from the squid proxy during Ignition fetch.Reverting to validate whether this change is the root cause of the hypershift-e2e-aws failures.
/jira CNTRLPLANE-3871
AI-generated. Review for accuracy.
@sosiouxme requested in Slack thread