MG-272: Add periodic CI jobs for Hypershift #81737
Conversation
|
@neha037: This pull request references MG-272 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.0." or "openshift-5.0.", but it targets "openshift-4.22" 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. |
WalkthroughAdds a multi-architecture 4.22 release candidate and a weekly AWS Hypershift CI job that installs must-gather-operator, verifies rollout, and runs end-to-end tests. ChangesMust-gather operator CI updates
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: neha037 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@ci-operator/config/openshift/must-gather-operator/openshift-must-gather-operator-release-4.22.yaml`:
- Around line 209-210: Add a finite --timeout value to the rollout status
command in the deployment install step, matching the timeout used by the other
rollout check in this file.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: 6610b378-073a-41f6-b98d-ea0daa817aac
⛔ Files ignored due to path filters (1)
ci-operator/jobs/openshift/must-gather-operator/openshift-must-gather-operator-release-4.22-periodics.yamlis excluded by!ci-operator/jobs/**
📒 Files selected for processing (1)
ci-operator/config/openshift/must-gather-operator/openshift-must-gather-operator-release-4.22.yaml
|
@neha037: |
|
/pj-rehearse |
1 similar comment
|
/pj-rehearse |
|
@neha037: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse |
|
@neha037: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@neha037: The following tests failed, say
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. |
Summary by CodeRabbit
ci-operator/config/openshift/must-gather-operator/openshift-must-gather-operator-release-4.22.yamlto add a newmulti-latestrelease candidate for OCP 4.22 (product: ocp,stream: nightly,architecture: multi), pinned viaRELEASE_IMAGE_LATEST: release:multi-latest.e2e-aws-hypershift-operator-weekly,@weekly) that runs against theopenshift-org-awscluster profile.--timeout=15m) and runsmake test-e2eusing theoptional-operators-ci-operator-sdk-hypershiftworkflow, mountingcase-management-creds; it also setsHYPERSHIFT_SKIP_VERSION_VALIDATION: "true".openshift-4.22(invalid formain); it should target5.0.*/openshift-5.0.*instead.