INTEROP-9450: Fix OPP preflight compat matrix for OCP 5.0 and 5.1 - #85225
openshift-merge-bot[bot] merged 2 commits into
Conversation
|
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: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review. WalkthroughThe OCP 5.0 OPP compatibility matrix now requires ChangesOPP compatibility
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The matrix now selects the ODF 4.22 channel for OCP 5.0, matching the available catalog channel. No concrete merge risk remains. 🚥 Pre-merge checks | ✅ 14 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/assign |
c4e7f80 to
674a4df
Compare
|
/pj-rehearse periodic-ci-stolostron-policy-collection-main-ocp4.22-upgrade-interop-opp-upgrade-aws |
|
/retest |
|
@amp-rh: your |
|
/retest AI-generated. Review for accuracy. |
ODF uses stable-4.x channel versioning, not 5.x. The v5.0 operator catalog only has stable-4.22 for ODF. Change odf-operator:5.0 to odf-operator:4.22 in the OPP_COMPAT["5.0"] entry. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
674a4df to
6db9803
Compare
|
@redhat-chai-bot: This pull request references INTEROP-9450 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 task to target the "5.1.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. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amp-rh, redhat-chai-bot 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 |
|
/pj-rehearse ack |
|
@amp-rh: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
…enshift#85225) * Fix ODF operator version in OPP preflight compat matrix for 5.0 ODF uses stable-4.x channel versioning, not 5.x. The v5.0 operator catalog only has stable-4.22 for ODF. Change odf-operator:5.0 to odf-operator:4.22 in the OPP_COMPAT["5.0"] entry. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Also fix OPP_COMPAT 5.1 row: remove unavailable operators Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Summary
Fixes the OPP preflight compatibility matrix so that OCP 5.0 and 5.1 interop jobs are not blocked by missing or unavailable operator versions.
Changes
OCP 5.0 row — lower
odf-operatorfrom5.0to4.22(ODF 5.0 is not yet available).OCP 5.1 row — remove
odf-operatorandrhacs-operator(neither is in the 5.1 catalog at all; the preflight gate marks NOT INSTALLED operators as failures), and lowerquay-operatorfrom3.18to3.17(only 3.17.4 is available).Before:
After:
Context
SKIP_POLICIESfor 5.1 test execution. Depends on this PR landing first.Jira: INTEROP-9450 / parent INTEROP-9329