OKD-387: Fix SCOS 4.22 shipping cri-o 1.36 instead of 1.35#81863
OKD-387: Fix SCOS 4.22 shipping cri-o 1.36 instead of 1.35#81863pskrbasu wants to merge 2 commits into
Conversation
…ease-4.22 The openshift/os master__okd-scos CI config builds from the master branch and promotes to scos-4.22. When master moved to target 5.0, c10s.repo was updated to point c10s-sig-cloud-okd at the okd-5.0 package repo, which contains cri-o 1.36.x instead of 1.35.x. Create a dedicated release-4.22__okd-scos config that builds from the release-4.22 branch (where c10s.repo correctly points to okd-4.22/), and remove scos-4.22 promotion from the master config.
|
@pskrbasu: This pull request references OKD-387 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 the "5.0.0" version, but no target version was set. 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. |
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (2)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughAdds an ChangesSCOS release configuration
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pskrbasu 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 |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse pull-ci-openshift-os-release-4.22-okd-scos-images |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@pskrbasu: The following test 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. |
|
For the rehearsal tests (ci/rehearse/openshift/os/release-4.22/okd-scos-images) to pass, this PR needs to be merged first - openshift/os#1947 |
Summary
openshift-os-master__okd-scosCI config builds from themasterbranch ofopenshift/osand promotes toscos-4.22. When master moved to target 5.0,c10s.repowas updated to pointc10s-sig-cloud-okdat theokd-5.0package repo (which has cri-o 1.36.x). Theokd-4.22repo only has cri-o 1.35.x.release-4.22__okd-scosconfig (matching the established pattern used for 4.21) and removesscos-4.22promotion from the master config.Test plan
make updategenerates correct Prow jobs for the new configrelease-4.22produces astream-coreosimage with cri-o 1.35.xSummary by CodeRabbit
release-4.22branch, ensuring cri-o 1.35.x is shipped instead of 1.36.release-4.22__okd-scosCI configuration with image builds, promotion targets, release integration, resources, and optional AWS OVN testing.scos-5.0rather thanscos-4.22.