Skip to content

Multiarch: Migrate ocp-heavy-build-ovn-remote-libvirt-multi-z-z to VPN and add for 4.21/4.22#76302

Draft
ibm-adarsh wants to merge 2 commits intoopenshift:mainfrom
ibm-adarsh:ocp-heavy-build-ovn-remote-libvirt-multi-z-z
Draft

Multiarch: Migrate ocp-heavy-build-ovn-remote-libvirt-multi-z-z to VPN and add for 4.21/4.22#76302
ibm-adarsh wants to merge 2 commits intoopenshift:mainfrom
ibm-adarsh:ocp-heavy-build-ovn-remote-libvirt-multi-z-z

Conversation

@ibm-adarsh
Copy link
Contributor

@ibm-adarsh ibm-adarsh commented Mar 16, 2026

Summary

  • Migrate ocp-heavy-build-ovn-remote-libvirt-multi-z-z (IBM Z) to VPN-based connectivity for OCP 4.17–4.20.
  • Add ocp-heavy-build-ovn-remote-libvirt-multi-z-z for OCP 4.21 and 4.22 with the same VPN-based setup.

Changes

VPN migration (4.17–4.20)

  • cluster_profile: libvirt-s390x-1 / libvirt-s390x-2 → libvirt-s390x-vpn
  • capabilities: sshd-bastion → intranet
  • workflow: openshift-e2e-libvirt-upi → openshift-e2e-libvirt-vpn
  • env: added USE_EXTERNAL_DNS: "true"

Aligns this job with other libvirt multi-z-z jobs (e.g. image-ecosystem, jenkins-e2e, e2e-serial) that already use VPN and external DNS.

New jobs (4.21, 4.22)

  • Added ocp-heavy-build-ovn-remote-libvirt-multi-z-z for IBM Z on 4.21 and 4.22.
  • Same VPN-based config: libvirt-s390x-vpn, intranet, USE_EXTERNAL_DNS: "true", openshift-e2e-libvirt-vpn.
  • Schedule: cron: 0 1 * * 2,4 (Tue/Thu 01:00 UTC).

Files modified

  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.17.yaml through 4.22.yaml
  • ci-operator/jobs/openshift/multiarch/openshift-multiarch-main-periodics.yaml (generated)

@ibm-adarsh
multiarch: ocp-heavy-build-ovn-remote-libvirt-multi-z-z VPN and add 4…
21bcbfa 
….21/4.22

- Migrate ocp-heavy-build-ovn-remote-libvirt-multi-z-z to VPN (4.17-4.20):
  cluster_profile libvirt-s390x-vpn, intranet capability, USE_EXTERNAL_DNS,
  workflow openshift-e2e-libvirt-vpn
- Add ocp-heavy-build-ovn-remote-libvirt-multi-z-z for IBM Z on 4.21 and 4.22
  with same VPN-based connectivity
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 16, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

[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 andymcc 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:

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

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Mar 16, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

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.

@sandisamp
Copy link

sandisamp commented Mar 16, 2026

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 16, 2026
@ibm-adarsh
multiarch: align ocp-heavy-build-ovn-remote-libvirt-multi-z-z cron fo…
5563eff 
…r 4.21/4.22

Follow +3h pattern from 4.17-4.20: 4.21 at 04:00 UTC, 4.22 at 07:00 UTC (Tue/Thu)
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 16, 2026

[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.21-ocp-heavy-build-ovn-remote-libvirt-multi-z-z N/A periodic Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.19-ocp-heavy-build-ovn-remote-libvirt-multi-z-z N/A periodic Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.18-ocp-heavy-build-ovn-remote-libvirt-multi-z-z N/A periodic Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-heavy-build-ovn-remote-libvirt-multi-z-z N/A periodic Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.20-ocp-heavy-build-ovn-remote-libvirt-multi-z-z N/A periodic Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.17-ocp-heavy-build-ovn-remote-libvirt-multi-z-z 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.

@ibm-adarsh
Copy link
Contributor Author

ibm-adarsh commented Mar 16, 2026

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.17-ocp-heavy-build-ovn-remote-libvirt-multi-z-z

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 16, 2026

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

@ibm-adarsh
Copy link
Contributor Author

ibm-adarsh commented Mar 16, 2026

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.18-ocp-heavy-build-ovn-remote-libvirt-multi-z-z

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 16, 2026

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

@ibm-adarsh
Copy link
Contributor Author

ibm-adarsh commented Mar 16, 2026

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.19-ocp-heavy-build-ovn-remote-libvirt-multi-z-z

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 16, 2026

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

@ibm-adarsh
Copy link
Contributor Author

ibm-adarsh commented Mar 16, 2026

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.20-ocp-heavy-build-ovn-remote-libvirt-multi-z-z

@ibm-adarsh
Copy link
Contributor Author

ibm-adarsh commented Mar 16, 2026

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.21-ocp-heavy-build-ovn-remote-libvirt-multi-z-z

@ibm-adarsh
Copy link
Contributor Author

ibm-adarsh commented Mar 16, 2026

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-heavy-build-ovn-remote-libvirt-multi-z-z

@ibm-adarsh
Copy link
Contributor Author

ibm-adarsh commented Mar 16, 2026

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.17-ocp-heavy-build-ovn-remote-libvirt-multi-z-z

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 16, 2026

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

@ibm-adarsh
Copy link
Contributor Author

ibm-adarsh commented Mar 16, 2026

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.18-ocp-heavy-build-ovn-remote-libvirt-multi-z-z

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 16, 2026

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

@ibm-adarsh
Copy link
Contributor Author

ibm-adarsh commented Mar 16, 2026

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.19-ocp-heavy-build-ovn-remote-libvirt-multi-z-z

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 16, 2026

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

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 16, 2026
@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Mar 16, 2026

PR needs rebase.

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.

@tvardema
Copy link
Contributor

tvardema commented Mar 16, 2026

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@ibm-adarsh @sandisamp @openshift-ci-robot @openshift-merge-robot @tvardema