Skip to content

Use libvirt-s390x-vpn-oz cluster profile for 5.0 s390x conformance-parallel jobs - #82651

Open
ibm-adarsh wants to merge 1 commit into
openshift:mainfrom
ibm-adarsh:use-vpn-oz-cluster-profile-5.0-s390x-conformance
Open

Use libvirt-s390x-vpn-oz cluster profile for 5.0 s390x conformance-parallel jobs#82651
ibm-adarsh wants to merge 1 commit into
openshift:mainfrom
ibm-adarsh:use-vpn-oz-cluster-profile-5.0-s390x-conformance

Conversation

@ibm-adarsh

@ibm-adarsh ibm-adarsh commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Switch cluster profile from libvirt-s390x-vpn to libvirt-s390x-vpn-oz for all conformance-parallel IBM Z (s390x) periodic jobs in OCP 5.0:

  • ocp-e2e-ovn-remote-libvirt-s390x
  • ocp-e2e-ovn-remote-libvirt-multi-z-z
  • ocp-e2e-ovn-agent-remote-libvirt-multi-z-z
  • ocp-fips-ovn-remote-libvirt-multi-z-z

Summary by CodeRabbit

Updates four OpenShift 5.0 s390x conformance-parallel periodic jobs to run on the libvirt-s390x-vpn-oz cluster profile, including the FIPS configuration.

…rallel jobs

Switch cluster profile from libvirt-s390x-vpn to libvirt-s390x-vpn-oz
for all conformance-parallel IBM Z (s390x) periodic jobs in OCP 5.0:

- ocp-e2e-ovn-remote-libvirt-s390x
- ocp-e2e-ovn-remote-libvirt-multi-z-z
- ocp-e2e-ovn-agent-remote-libvirt-multi-z-z
- ocp-fips-ovn-remote-libvirt-multi-z-z
@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 701e5711-f446-4731-9833-3b4da2115e1e

📥 Commits

Reviewing files that changed from the base of the PR and between a4d26cf and 4eafc88.

⛔ 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 (1)
  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml

Walkthrough

Four s390x remote-libvirt nightly test configurations now reference the libvirt-s390x-vpn-oz cluster profile instead of libvirt-s390x-vpn.

Changes

s390x profile update

Layer / File(s) Summary
Update remote-libvirt cluster profiles
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
Four remote libvirt test jobs, including the agent and FIPS variants, use libvirt-s390x-vpn-oz.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested reviewers: sandeepknd

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the PR’s main change: switching 5.0 s390x jobs to the libvirt-s390x-vpn-oz cluster profile.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed No Ginkgo test titles were added or modified; the PR only changes CI cluster-profile settings in YAML job configs.
Test Structure And Quality ✅ Passed PR only changes CI YAML cluster profile labels; no Ginkgo test code or test structure is present to evaluate.
Microshift Test Compatibility ✅ Passed PASS: The PR only updates CI/job YAML cluster_profile labels for four periodic jobs; no new Ginkgo tests or test bodies were added.
Single Node Openshift (Sno) Test Compatibility ✅ Passed Only ci-operator/job config changed; no new or modified Ginkgo tests, so SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR only updates ci-operator cluster_profile values for s390x periodic jobs; no manifests, controllers, or scheduling constraints were changed.
Ote Binary Stdout Contract ✅ Passed Only CI YAML changed; no Go/test harness code or stdout writes were introduced, so the OTE stdout contract isn’t implicated.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Touched file is CI job config only; no Ginkgo test definitions or network-using test code were added, just cluster_profile swaps.
No-Weak-Crypto ✅ Passed Changed YAML only swaps cluster_profile names for s390x jobs; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons appear.
Container-Privileges ✅ Passed Only cluster_profile values changed in the CI config; no privileged/hostNetwork/hostIPC/SYS_ADMIN/allowPrivilegeEscalation fields are present.
No-Sensitive-Data-In-Logs ✅ Passed Only cluster_profile values changed in a YAML config; no log statements or sensitive data (passwords, tokens, PII, hostnames) were introduced.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

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

@openshift-ci
openshift-ci Bot requested review from hamzy and prb112 July 30, 2026 05:56
@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 Jul 30, 2026
@openshift-ci

openshift-ci Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

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-merge-bot

Copy link
Copy Markdown
Contributor

[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-5.0-ocp-e2e-ovn-agent-remote-libvirt-multi-z-z N/A periodic Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-e2e-ovn-remote-libvirt-multi-z-z N/A periodic Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-e2e-ovn-remote-libvirt-s390x N/A periodic Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-fips-ovn-remote-libvirt-multi-z-z N/A periodic Ci-operator config 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.

@v78singh

Copy link
Copy Markdown

/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 Jul 30, 2026
@ibm-adarsh

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-e2e-ovn-remote-libvirt-multi-z-z

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@v78singh

v78singh commented Jul 30, 2026

Copy link
Copy Markdown

/lgtm

@v78singh

Copy link
Copy Markdown

/approve

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 30, 2026
@ibm-adarsh

Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jul 30, 2026
@ibm-adarsh

Copy link
Copy Markdown
Contributor Author

/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 Jul 30, 2026
@ibm-adarsh

Copy link
Copy Markdown
Contributor Author

@amrutp-redhat @v78singh I am keeping this on hold because as per Infra team, timing mismatch for older vpn profile get's fixed.
@amrutp-redhat Please see the next periodic run of 5.0, it it passes the bootstrap phase, we will close this PR else will merge it.

@openshift-ci

openshift-ci Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

@ibm-adarsh: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@v78singh

Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 30, 2026
@openshift-ci

openshift-ci Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ibm-adarsh, v78singh

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

The pull request process is described 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants