NO-ISSUE: Consider centos-10 stream for OKD clusters - #31487
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
@pablintino: This pull request explicitly references no 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)
🚧 Files skipped from review as they are similar to previous changes (1)
Walkthrough
ChangesStandalone node OS validation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 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: pablintino 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 |
|
/pipeline required |
|
Scheduling required tests: |
4ef1c9c to
09a3843
Compare
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
/pipeline required |
|
Scheduling required tests: |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 09a3843
New tests seen in this PR at sha: 09a3843
|
09a3843 to
06e7ed3
Compare
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
This change adds centos-10 as the expected stream of OKD jobs. From now, jobs named *okd* should always match the only available stream, centos-10. Signed-off-by: Pablo Rodriguez Nava <git@amail.pablintino.eu>
06e7ed3 to
c30e4d8
Compare
|
@pablintino: 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. |
|
/pipeline required |
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
Scheduling required tests: |
| clusterVersion, err := oc.AdminConfigClient().ConfigV1().ClusterVersions().Get(context.Background(), "version", metav1.GetOptions{}) | ||
| o.Expect(err).NotTo(o.HaveOccurred(), "Error getting ClusterVersion version singleton") | ||
|
|
||
| isOKD := strings.Contains(clusterVersion.Status.Desired.Version, "okd-scos") |
There was a problem hiding this comment.
It feels like these checks don't really belong in validateStandaloneNodeOS
Could this isOKD logic / name check be above https://github.com/pablintino/origin/blob/c30e4d8664ac0dd3ebda399ef73d8ab911ec3c12/test/extended/ci/job_names.go#L179
Understand that will lead to a duplicate isOKD check as you need that for the targetStream as well.
This change adds centos-10 as the expected stream of OKD jobs. From now, jobs named okd should always match the only available stream, centos-10.
Summary by CodeRabbit
okd-scosjob naming.