[DO NOT MERGE] MULTIARCH 4.16.69 PPC64LE infra rehearse

[tonyxrmdavidson]

Summary by CodeRabbit

Renames the PPC64LE remote S2S Libvirt test jobs in the OpenShift 4.16 multiarch CI configurations. The new names add the -test-1 suffix for both standard OVN and FIPS OVN jobs.

[tonyxrmdavidson]

/pj-rehearse

[openshift-merge-bot]

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

[coderabbitai]

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: 8cf8b418-304d-4a55-959f-5efa145430a1

📥 Commits

Reviewing files that changed from the base of the PR and between b9f267e and 11b80d0.

⛔ 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.16-upgrade-from-nightly-4.15.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.16.yaml

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

Walkthrough

Changes

PPC64LE test identifier renames

Layer / File(s)	Summary
Rename remote S2S Libvirt test identifiers ci-operator/config/openshift/multiarch/*	The upgrade configuration renames the PPC64LE remote S2S Libvirt test. The FIPS configuration appends -test-1 to its test identifier. Execution settings remain unchanged.

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

Merge Risk: ⚪ Minimal · up to 11b80

This CI configuration change introduces no identified correctness, security, availability, or deployment risk. No actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 10

✅ Passed checks (10 passed)

Check name	Status	Explanation
Stable And Deterministic Test Names	✅ Passed	PASS: The pull request changes only static CI target and generated Prow job names. The diff changes two YAML as values and matching name/--target values to add the fixed suffix -test-1. It int…
Test Structure And Quality	✅ Passed	PASS: The commit changes only three YAML files. The diff renames two PPC64LE test targets and their generated periodic job names/arguments. It does not add or modify Ginkgo test code, It blocks, setup…
Microshift Test Compatibility	✅ Passed	The pull request adds no Ginkgo tests. The complete diff changes only three YAML files and renames two PPC64LE CI targets plus their generated periodic job names and target arguments. No test bodies, …
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS: The pull request adds no Ginkgo e2e tests. The complete HEAD diff changes only two CI configuration targets and their generated periodic job names and arguments. No Go files or It(), Describe(),…
Topology-Aware Scheduling Compatibility	✅ Passed	PASS: The commit changes only CI test names and matching ci-operator target references in two test configuration files and one generated Prow job file. The diff adds no deployment manifests, operato…
Ote Binary Stdout Contract	✅ Passed	PASS: The pull request changes only YAML test/job names and matching ci-operator --target values. The exact diff contains no Go or OTE implementation changes and no process-level stdout writes such …
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PASS: The pull request does not add or modify Ginkgo e2e tests. The diff contains only YAML changes that rename two PPC64LE test targets and their generated periodic jobs. No It(), Describe(), `Co…
No-Weak-Crypto	✅ Passed	PASS: The pull request changes only test and generated Prow job names and targets. The exact commit diff contains no MD5, SHA1, DES, RC4, Blowfish, ECB, custom crypto implementation, or non-constant-t…
Container-Privileges	✅ Passed	PASS. The pull-request diff only renames two test identifiers and updates their generated Prow job names and targets. No changed line adds privileged: true, hostPID, hostNetwork, hostIPC, `SYS…
No-Sensitive-Data-In-Logs	✅ Passed	PASS. The commit changes only two test identifiers and their generated Prow job names and --target values. The exact diff adds no logging statements or sensitive values such as passwords, tokens, AP…

Full details: Stable And Deterministic Test Names

Explanation

PASS: The pull request changes only static CI target and generated Prow job names. The diff changes two YAML as values and matching name/--target values to add the fixed suffix -test-1. It introduces no Ginkgo It, Describe, Context, or When title and no dynamic value such as a timestamp, UUID, node, namespace, pod name, or IP address.

Full details: Test Structure And Quality

Explanation

PASS: The commit changes only three YAML files. The diff renames two PPC64LE test targets and their generated periodic job names/arguments. It does not add or modify Ginkgo test code, It blocks, setup, cleanup, waits, or assertions. Therefore none of the stated Ginkgo quality failure conditions apply.

Full details: Microshift Test Compatibility

Explanation

The pull request adds no Ginkgo tests. The complete diff changes only three YAML files and renames two PPC64LE CI targets plus their generated periodic job names and target arguments. No test bodies, OpenShift API references, namespaces, or MicroShift-unsupported assumptions were added.

Full details: Single Node Openshift (Sno) Test Compatibility

Explanation

PASS: The pull request adds no Ginkgo e2e tests. The complete HEAD diff changes only two CI configuration targets and their generated periodic job names and arguments. No Go files or It(), Describe(), Context(), or When() declarations changed. The SNO test compatibility check is therefore not applicable.

Full details: Topology-Aware Scheduling Compatibility

Explanation

PASS: The commit changes only CI test names and matching ci-operator target references in two test configuration files and one generated Prow job file. The diff adds no deployment manifests, operator/controller code, or scheduling constraints such as affinity, topology spread, replica, node selector, toleration, or PDB settings. The custom check is therefore not applicable.

Full details: Ote Binary Stdout Contract

Explanation

PASS: The pull request changes only YAML test/job names and matching ci-operator --target values. The exact diff contains no Go or OTE implementation changes and no process-level stdout writes such as fmt.Print*, klog, or suite setup code. Therefore, the OTE JSON stdout contract is not affected.

Full details: Ipv6 And Disconnected Network Test Compatibility

Explanation

PASS: The pull request does not add or modify Ginkgo e2e tests. The diff contains only YAML changes that rename two PPC64LE test targets and their generated periodic jobs. No It(), Describe(), Context(), or When() declarations, IPv4 assumptions, or external connectivity requirements were introduced.

Full details: No-Weak-Crypto

Explanation

PASS: The pull request changes only test and generated Prow job names and targets. The exact commit diff contains no MD5, SHA1, DES, RC4, Blowfish, ECB, custom crypto implementation, or non-constant-time secret comparison. No weak-crypto condition is introduced.

Full details: Container-Privileges

Explanation

PASS. The pull-request diff only renames two test identifiers and updates their generated Prow job names and targets. No changed line adds privileged: true, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation: true, or a root security context. The existing capabilities entries are unchanged Prow capability labels, not added Linux capabilities.

Full details: No-Sensitive-Data-In-Logs

Explanation

PASS. The commit changes only two test identifiers and their generated Prow job names and --target values. The exact diff adds no logging statements or sensitive values such as passwords, tokens, API keys, PII, session IDs, hostnames, or customer data. Existing secret-related arguments are unchanged context.

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tonyxrmdavidson
Once this PR has been reviewed and has the lgtm label, please assign deepsm007 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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@tonyxrmdavidson: 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.16-upgrade-from-nightly-4.15-ocp-ovn-remote-s2s-libvirt-ppc64le-test-1	N/A	periodic	Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.16-ocp-fips-ovn-remote-s2s-libvirt-ppc64le-test-1	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.

[atewari-rh]

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.16-ocp-fips-ovn-remote-s2s-libvirt-ppc64le-test-1

[openshift-merge-bot]

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

[openshift-ci]

@tonyxrmdavidson: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/rehearse/periodic-ci-openshift-multiarch-main-nightly-4.16-ocp-fips-ovn-remote-s2s-libvirt-ppc64le-test-1	11b80d0	link	unknown	/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.16-ocp-fips-ovn-remote-s2s-libvirt-ppc64le-test-1
ci/rehearse/periodic-ci-openshift-multiarch-main-nightly-4.16-upgrade-from-nightly-4.15-ocp-ovn-remote-s2s-libvirt-ppc64le-test-1	11b80d0	link	unknown	/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.16-upgrade-from-nightly-4.15-ocp-ovn-remote-s2s-libvirt-ppc64le-test-1

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.