INTEROP-9509: Fix upi-installer via base_images, activate OPP crons, and add SKIP_POLICIES for 5.1 - #85532
INTEROP-9509: Fix upi-installer via base_images, activate OPP crons, and add SKIP_POLICIES for 5.1#85532redhat-chai-bot wants to merge 1 commit into
Conversation
|
@redhat-chai-bot: This pull request references INTEROP-9509 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.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. |
|
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 ignored due to path filters (1)
📒 Files selected for processing (7)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. WalkthroughThe change updates four policy-collection test schedules and replaces legacy ChangesCI configuration updates
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Suggested reviewers: 🚥 Pre-merge checks | ✅ 14 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
fae2da8 to
00156d9
Compare
|
/pj-rehearse periodic-ci-stolostron-policy-collection-main-ocp5.1-upgrade-interop-opp-upgrade-aws AI-generated. Review for accuracy. |
|
@redhat-chai-bot: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-RedHatQE-interop-testing-master-opp--ocp-5.1-lpMainline-lp-interop-cr--full-stack--vsphere AI-generated. Review for accuracy. |
|
@redhat-chai-bot: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
00156d9 to
c28b2bb
Compare
…d OPP cron schedules Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
c28b2bb to
bc69b33
Compare
|
/pj-rehearse periodic-ci-RedHatQE-interop-testing-master-opp--ocp-4.22-lpMainline-lp-interop-cr--full-stack--vsphere AI-generated. Review for accuracy. |
|
/pj-rehearse periodic-ci-stolostron-policy-collection-main-ocp5.0-upgrade-interop-opp-upgrade-aws AI-generated. Review for accuracy. |
|
@redhat-chai-bot: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
1 similar comment
|
@redhat-chai-bot: 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: |
|
/assign amp-rh AI-generated. Review for accuracy. |
|
@redhat-chai-bot: 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. |
|
/retest AI-generated. Review for accuracy. |
|
/pj-rehearse ack AI-generated. Review for accuracy. |
|
@redhat-chai-bot: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[APPROVALNOTIFIER] This PR is NOT 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. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
⏰ Approval urgency — Sep 21 03:00 UTC cron batch This PR needs Why it matters: This PR unblocks 4 of 6 failing OPP interop periodic jobs (upi-installer fix for 4.22, SKIP_POLICIES for 5.1, stolostron cron activation). Without it, the Q3 interop pass rate stays under 1% against a 90% target — deadline Sep 30. Could an approver please review and AI-generated. Review for accuracy. |
|
/retest Re-triggering failed rehearsals (stolostron-policy-collection upgrade + vsphere full-stack). Both failed overnight — likely infra flakes on shared cloud resources during Sunday batch. AI-generated. Review for accuracy. |
Merge Readiness SummaryAll CI checks pass ✅ — the core change (upi-installer via Rehearsal failures are NOT caused by this PR — both are pre-existing downstream issues:
These rehearsals are already acknowledged via ⏳ Merge Blocker: Missing
|
|
Hi — this PR is the last piece blocking our P0 gate for Interop OPP testing enablement. The code has The remaining approval zones are:
cc @dhaiducek @JustinKuli @smg247 @danilo-gemoli AI-generated. Review for accuracy. |
|
/hold Holding — superseded by single batch PR combining all OPP interop fixes (see INTEROP-9509). Will close this PR after the batch PR merges. AI-generated. Review for accuracy. |
|
/assign @amp-rh AI-generated. Review for accuracy. |
|
Superseded by #85540, which includes all changes from this PR (upi-installer base_image fix, SKIP_POLICIES for 5.1, stolostron cron activation) plus additional scope: acm-tests-observability removal, FIPS configs, OCS test coverage, and SKIP_POLICIES for 5.0. Closing to avoid merge conflicts. AI-generated. Review for accuracy. |
|
Closing — superseded by batch PR #85540 which combines all OPP interop fixes (Sources A–D + review fixes + FIPS configs). AI-generated. Review for accuracy. |
What
Three fixes for OPP interop CI jobs, all scoped to OPP-owned configs:
1. Fix
upi-installerImagePullBackOff viabase_imagesoverride (3 config files)Shared IPI step-registry refs use
from: upi-installer, which resolves tostable:upi-installer. Sinceupi-installerisn't in the release payload, this causes ImagePullBackOff. Instead of modifying shared step-registry refs (which affect 2,472 jobs), this addsupi-installertobase_imagesin each affected OPP config. ci-operator checksbase_imagesfirst, sofrom: upi-installerresolves topipeline:upi-installer(imported fromocp/4.18:upi-installer).Configs modified:
stolostron-policy-collection-main__ocp5.0-upgrade.yaml(usesipi-conf-aws-rootvolume)stolostron-policy-collection-main__ocp5.1-upgrade.yaml(usesipi-conf-aws-rootvolume)RedHatQE-interop-testing-master__opp--ocp-4.22-lpMainline-lp-interop.yaml(uses all 3 affected IPI steps — AWS + vSphere)2. Activate disabled OPP cron schedules (4 config files)
Four stolostron/policy-collection periodic configs had the placeholder cron
0 23 31 2 *(February 31 — never fires). Changed to0 3,15 * * *to run twice daily.3. Add SKIP_POLICIES for OPP 5.1 (2 config files + 1 step-registry declaration)
OPP 5.1 jobs fail because ACS and Quay operators are not present in the v5.1 catalog. Added
SKIP_POLICIESenv var to skip the 21 affected policy names until the operators ship.Related
Validation
make ci-operator-config— exit 0make jobs— exit 0