MG-272: Add weekly HyperShift periodic e2e job for must-gather-operator - #82203
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@neha037: This pull request references MG-272 which is a valid jira issue. 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. |
|
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: Enterprise Run ID: 📒 Files selected for processing (1)
WalkthroughAdds a multi-architecture nightly release candidate and a weekly AWS Hypershift operator E2E job that installs, verifies, and tests the deployment. ChangesHypershift E2E validation
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 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. 🔧 Checkov (3.3.8)ci-operator/config/openshift/must-gather-operator/openshift-must-gather-operator-master.yamlTraceback (most recent call last): Comment |
|
/pj-rehearse |
|
@neha037: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Add multi-arch release image override and version validation skip to fix arm64 architecture mismatch in hypershift rehearsal. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
/pj-rehearse |
|
@neha037: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-must-gather-operator-master-e2e-hypershift-operator |
|
/pj-rehearse abort |
|
@neha037: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
1 similar comment
|
@neha037: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/retest |
1 similar comment
|
/retest |
|
/pj-rehearse |
|
@neha037: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse e2e-hypershift-operator |
|
@shivprakashmuley: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@shivprakashmuley: job(s): e2e-hypershift-operator either don't exist or were not found to be affected, and cannot be rehearsed |
|
/pj-rehearse periodic-ci-openshift-must-gather-operator-master-e2e-hypershift-operator |
|
@neha037: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@neha037, |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse periodic-ci-openshift-must-gather-operator-master-e2e-hypershift-operator |
|
@neha037: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-must-gather-operator-master-e2e-hypershift-operator |
|
@neha037: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
| cluster_profile: openshift-org-aws | ||
| dependencies: | ||
| OO_BUNDLE: must-gather-operator-bundle | ||
| RELEASE_IMAGE_LATEST: release:multi-latest |
There was a problem hiding this comment.
The hypershift-hostedcluster-create-hostedcluster step uses the RELEASE_IMAGE_LATEST dependency to determine which OCP release image to deploy on the hosted cluster. By default, it resolves to release:latest, which is the single-arch (amd64) integration release defined in the config.
The problem is that HyperShift hosted clusters require a multi-architecture release image. If you don't override this dependency, the hosted cluster creation will use the single-arch release:latest and fail because HyperShift needs multi-arch support.
This line overrides the default dependency mapping so that the workflow step receives the release:multi-latest payload (the multi-arch OCP 5.0 nightly candidate defined in Change 1) instead of the single-arch release:latest.
| OO_BUNDLE: must-gather-operator-bundle | ||
| RELEASE_IMAGE_LATEST: release:multi-latest | ||
| env: | ||
| HYPERSHIFT_SKIP_VERSION_VALIDATION: "true" |
There was a problem hiding this comment.
HYPERSHIFT_SKIP_VERSION_VALIDATION is required because we create the hosted cluster from a multi-arch nightly (multi-latest) while the hypershift CLI / operator come from a separately updated CI image — those versions often don’t match, and without the skip, hosted-cluster creation fails the release-image version check.
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neha037, shivprakashmuley The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
/pj-rehearse ack |
|
@shivprakashmuley: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-merge-bot
Bot
added
the
rehearsals-ack
b04a2f8
into
openshift:main
![openshift-prow[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…or (openshift#82203) * MG-272: add hypershift periodic * MG-272: add multi-latest release for hypershift periodic Add multi-arch release image override and version validation skip to fix arm64 architecture mismatch in hypershift rehearsal. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
3 participants
Summary
e2e-hypershift-operator) for the must-gather-operator master branch running on a HyperShift hosted clusteroptional-operators-ci-operator-sdk-hypershiftworkflow withopenshift-org-awscluster profilee2e-gcp-operatorpresubmit (install verification +make test-e2ewith case-management-creds)Test plan
make updateran successfully and generated the periodic job fileperiodic-ci-openshift-must-gather-operator-master-e2e-hypershift-operatoruses correct workflow and AWS cluster profileJira: https://redhat.atlassian.net/browse/MG-272
🤖 Generated with Claude Code
Summary by CodeRabbit
This PR updates OpenShift CI configuration for the
must-gather-operatormaster branch by adding a weekly HyperShift end-to-end periodic job,periodic-ci-openshift-must-gather-operator-master-e2e-hypershift-operator. The new Prow job runs theoptional-operators-ci-operator-sdk-hypershiftworkflow using theopenshift-org-awscluster profile, pulls the operator from themust-gather-operator-bundle, setsRELEASE_IMAGE_LATESTfrom a new multi-archreleases.multi-latestcandidate, and enablesHYPERSHIFT_SKIP_VERSION_VALIDATIONto avoid the ARM64 HyperShift rehearsal version mismatch. It installs/verifies the operator rollout viaoc rollout statusand then executesmake test-e2ewith case-management credentials mounted into the test container.make updatecompleted successfully; CI rehearsal is still pending.