Remove unused OCP release import from operator e2e configs - #82262
Remove unused OCP release import from operator e2e configs#82262dustman9000 wants to merge 1 commit into
Conversation
The operator e2e jobs import the full OCP release payload (197 images) but never use any release images. The rosa-cluster-lease workflow only needs rosa-aws-cli. Removing the release import eliminates the release-images-latest pod, reducing build cluster pressure and avoiding scheduling delays.
|
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 ignored due to path filters (15)
📒 Files selected for processing (5)
💤 Files with no reviewable changes (5)
WalkthroughFive OpenShift CI operator configurations remove their ChangesRelease Pin Removal
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[REHEARSALNOTIFIER]
A total of 45 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse pull-ci-openshift-configure-alertmanager-operator-master-rosa-sts-e2e pull-ci-openshift-route-monitor-operator-master-rosa-sts-e2e pull-ci-openshift-managed-upgrade-operator-master-rosa-sts-e2e |
|
@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-configure-alertmanager-operator-master-rosa-sts-e2e-promotion-int periodic-ci-openshift-route-monitor-operator-master-rosa-sts-e2e-promotion-stage periodic-ci-openshift-managed-upgrade-operator-master-rosa-sts-e2e-promotion-int |
|
@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
Closing: ci-operator requires |
|
@dustman9000: 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
Remove the
releases.latestblock from all 5 SRE operator e2e ci-operator configs (RMO, CAMO, AVO, MUO, OAO).Context
The operator e2e jobs import the full OCP release payload (~197 images) via
releases.latest.candidatebut never use any release images. Therosa-cluster-lease-e2e-workflowonly usesrosa-aws-clias a base image.The release import creates a
release-images-latestpod that takes ~2 minutes to pull and tag 197 images. During build cluster pressure (DiskPressure, scheduling delays), this pod was stuck in Pending for over an hour, causing the entire promotion job to fail before any test steps ran.Removing it eliminates an unnecessary pod, reduces build cluster pressure, and speeds up job startup by ~2 minutes.
Jira: https://redhat.atlassian.net/browse/ROSAENG-60066
Test plan
Summary by CodeRabbit
release-images-latestpod.