multiarch: shift IBM Z s390x libvirt midnight jobs to 00:30 UTC - #84699
multiarch: shift IBM Z s390x libvirt midnight jobs to 00:30 UTC#84699ibm-adarsh wants to merge 1 commit into
Conversation
The OCP image-pruner CronJob runs at 00:00 UTC (default schedule:"")
on all build farm clusters. Any CI job that also starts at 00:00 UTC
races with the pruner: partially-written blob layers in the ephemeral
ci-op-* namespace can be deleted mid-import, leaving MTO with a broken
manifest ("manifest unknown"). MTO then cannot set a nodeAffinity,
the pod is scheduled randomly across amd64/aarch64 nodes, and an
arm64-node landing produces ImagePullBackOff for the amd64-only image.
PR openshift#83574 already shifted the ppc64le Power jobs from 00:00 -> 00:30.
This PR applies the same fix to ALL s390x (IBM Z) libvirt jobs that
were still at 00:00 UTC across OCP 4.14-4.23 and 5.0-5.1.
Jobs changed:
4.14: ocp-e2e-ovn-remote-libvirt-s390x (weekly)
ocp-image-ecosystem-ovn-remote-libvirt-s390x (Jan 12)
ocp-e2e-serial-ovn-remote-libvirt-s390x (Jan 14)
4.15: ocp-e2e-ovn-remote-libvirt-s390x-heterogeneous (Jan 9)
ocp-image-ecosystem-ovn-remote-libvirt-s390x (Jan 20)
ocp-e2e-serial-ovn-remote-libvirt-s390x (Jan 22)
4.16: ocp-e2e-ovn-remote-libvirt-s390x-heterogeneous (Jan 25)
ocp-image-ecosystem-ovn-remote-libvirt-s390x (Jan 28)
ocp-e2e-serial-ovn-remote-libvirt-s390x (Jan 30)
4.17: ocp-e2e-ovn-remote-libvirt-multi-z-z (Feb 5)
ocp-e2e-ovn-agent-remote-libvirt-multi-z-z (Feb 13)
ocp-image-ecosystem-ovn-remote-libvirt-multi-z-z (Feb 11)
ocp-e2e-serial-ovn-remote-libvirt-multi-z-z (Feb 8)
4.18: ocp-e2e-ovn-remote-libvirt-multi-z-z (Feb 16)
ocp-e2e-ovn-agent-remote-libvirt-multi-z-z (Feb 24)
ocp-e2e-ovn-remote-libvirt-multi-z-xz (Feb 27)
ocp-image-ecosystem-ovn-remote-libvirt-multi-z-z (Feb 22)
ocp-e2e-serial-ovn-remote-libvirt-multi-z-z (Feb 19)
4.20: ocp-e2e-ovn-remote-libvirt-s390x (Mon+Wed)
ocp-e2e-ovn-remote-libvirt-multi-z-z (Tue+Thu)
ocp-e2e-ovn-remote-libvirt-multi-z-xz (Tue+Thu)
ocp-image-ecosystem-ovn-remote-libvirt-multi-z-z (Sun)
ocp-e2e-serial-ovn-remote-libvirt-multi-z-z (Sat)
4.21: ocp-e2e-ovn-remote-libvirt-multi-z-xz (Tue+Thu)
4.22: ocp-e2e-ovn-remote-libvirt-multi-z-xz (Tue+Thu)
4.23: ocp-e2e-ovn-remote-libvirt-s390x, multi-z-z, z-xz,
agent, serial, fips, image-ecosystem, techpreview
upgrade-from-nightly-4.22 multi-z-z (Mar 24)
5.0: ocp-e2e-ovn-remote-libvirt-multi-z-xz (Tue+Thu)
5.1: ocp-e2e-ovn-remote-libvirt-multi-z-xz (Tue+Thu)
No ppc64le/Power jobs were modified.
Fixes: OCPBUGS-105501
Signed-off-by: Bob
|
Hi @ibm-adarsh. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
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: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (12)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. WalkthroughThe change updates 36 cron schedules across 12 multiarch CI configuration files. Each affected libvirt test job moves from minute 0 to minute 30 while retaining its existing hour, day, and weekday fields. ChangesMultiarch CI schedule updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to The affected s390x/libvirt CI jobs will start 30 minutes later while retaining their existing schedules otherwise. The configuration-only change is ready to merge with no identified current-head risk. 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: ibm-adarsh 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]
A total of 36 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: |
OCPBUGS-105501:
Why shifting to 00:30 fixes it
By 00:30 UTC the image-pruner has finished. ci-operator imports base images into a
clean namespace with no concurrent pruner activity → MTO reads the manifest cleanly
Ex: → sets
amd64nodeAffinity → pod always runs on an amd64 node → pull succeeds.PR #83574 applied this same fix to the ppc64le Power jobs and clean runs were
observed on the next scheduled execution. This PR applies the identical fix to all
s390x / IBM Z libvirt jobs that remained at midnight UTC.
Confirmed Failing Jobs (from OCPBUGS-105501)
ocp-e2e-ovn-remote-libvirt-s390xocp-e2e-ovn-remote-libvirt-s390xocp-e2e-ovn-remote-libvirt-multi-z-zFor context, the equivalent ppc64le jobs fixed by #83574:
ocp-e2e-ovn-remote-s2s-libvirt-ppc64leocp-e2e-ovn-remote-s2s-libvirt-multi-p-pocp-e2e-ovn-remote-s2s-libvirt-ppc64leWhat Changed
All changes are cron-only:
0 0 …→30 0 …UTC.No job configuration, workflow, cluster profile, or step-registry entry was modified.
Zero ppc64le / Power jobs were touched.
nightly-4.14nightly-4.15nightly-4.16nightly-4.17nightly-4.18nightly-4.20nightly-4.21nightly-4.22nightly-4.23nightly-4.23-upgrade-from-nightly-4.22nightly-5.0nightly-5.1openshift-multiarch-main-periodics.yamlTotal: 37 cron entries shifted across 13 files.
Summary by CodeRabbit
00:00to00:30UTC across OCP 4.14–4.23 and 5.0–5.1 CI configurations.