[WIP]: multiarch: migrate 4.13 s390x and 4.14-from-4.13 upgrade to libvirt-s390x-vpn

[ibm-adarsh]

Summary

Follow-up to #82603 / #83139: migrate OCP 4.13 homogeneous IBM Z jobs and the nightly-4.14-upgrade-from-nightly-4.13 upgrade to libvirt-s390x-vpn.

Jobs migrated

Config	Job	Profile	Workflow
nightly-4.13	ocp-e2e-ovn-remote-libvirt-s390x	libvirt-s390x-vpn	openshift-e2e-libvirt-vpn
nightly-4.13	ocp-image-ecosystem-ovn-remote-libvirt-s390x	libvirt-s390x-vpn	openshift-e2e-libvirt-vpn
nightly-4.13	ocp-e2e-serial-ovn-remote-libvirt-s390x	libvirt-s390x-vpn	openshift-e2e-libvirt-vpn
nightly-4.13	ocp-fips-ovn-remote-libvirt-s390x	libvirt-s390x-vpn	openshift-e2e-libvirt-vpn-fips
nightly-4.14-upgrade-from-nightly-4.13	ocp-ovn-remote-libvirt-s390x	libvirt-s390x-vpn	openshift-e2e-libvirt-vpn

Migrated jobs are pinned to build12 in generated periodics. Relies on the ≤4.15 s390x install fallbacks from #82603. STATIC_POD_CHECK_WORKAROUND is preserved on the 4.13 e2e/serial jobs.

Not in this PR: heterogeneous

Heterogeneous libvirt jobs still use libvirt-s390x-amd64 and need a dedicated VPN-OZ hetero profile/workflow.

Test plan

• Rehearse all migrated jobs (command below)
• Confirm 4.13 s390x logs use virsh when virt-install is absent
• Confirm upgrade installs 4.13 via VPN then upgrades to 4.14

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-e2e-ovn-remote-libvirt-s390x periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-image-ecosystem-ovn-remote-libvirt-s390x periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-e2e-serial-ovn-remote-libvirt-s390x periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-fips-ovn-remote-libvirt-s390x periodic-ci-openshift-multiarch-main-nightly-4.14-upgrade-from-nightly-4.13-ocp-ovn-remote-libvirt-s390x

[coderabbitai]

Warning

Review limit reached

@ibm-adarsh, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 31 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 3a27e60d-c0a9-4032-ac1a-b17bf433be9d

📥 Commits

Reviewing files that changed from the base of the PR and between b623641 and 2989687.

⛔ Files ignored due to path filters (1)

• ci-operator/jobs/openshift/multiarch/openshift-multiarch-main-periodics.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (2)

• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.13.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.14-upgrade-from-nightly-4.13.yaml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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 kubernetes-sigs/prow repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ibm-adarsh
Once this PR has been reviewed and has the lgtm label, please assign hamzy for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/multiarch/OWNERS
• ci-operator/jobs/openshift/multiarch/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ibm-adarsh]

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-e2e-ovn-remote-libvirt-s390x periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-image-ecosystem-ovn-remote-libvirt-s390x periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-e2e-serial-ovn-remote-libvirt-s390x periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-fips-ovn-remote-libvirt-s390x periodic-ci-openshift-multiarch-main-nightly-4.14-upgrade-from-nightly-4.13-ocp-ovn-remote-libvirt-s390x

[openshift-merge-bot]

@ibm-adarsh: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-merge-bot]

@ibm-adarsh: needs-ok-to-test label found, no rehearsals will be run

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@ibm-adarsh: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-multiarch-main-nightly-4.14-upgrade-from-nightly-4.13-ocp-ovn-remote-libvirt-s390x	N/A	periodic	Periodic changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@ibm-adarsh: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-multiarch-main-nightly-4.14-upgrade-from-nightly-4.13-ocp-ovn-remote-libvirt-s390x	N/A	periodic	Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-e2e-ovn-remote-libvirt-s390x	N/A	periodic	Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-e2e-serial-ovn-remote-libvirt-s390x	N/A	periodic	Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-fips-ovn-remote-libvirt-s390x	N/A	periodic	Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.13-ocp-image-ecosystem-ovn-remote-libvirt-s390x	N/A	periodic	Periodic changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.