MULTIARCH-6023: Updated 5.0 TechPreviewNoUpgrade serial ppc64le job cron timing

[KeerthanaAP]

Summary by CodeRabbit

Updated the OpenShift openshift/release multi-arch nightly 5.0 prow configuration on main to change the schedule for ocp-e2e-serial-ovn-techpreview-remote-s2s-libvirt-multi-p-p (ppc64le, intranet; cluster_profile: libvirt-ppc64le-s2s, FEATURE_SET: TechPreviewNoUpgrade, TEST_TYPE: conformance-serial). Specifically, its cron expression was adjusted from 0 13 * * 6 to 0 13 * * 5, moving the TechPreviewNoUpgrade serial conformance run to a different day-of-week while keeping all job steps and parameters the same.

[openshift-ci-robot]

@KeerthanaAP: This pull request references MULTIARCH-6023 which is a valid jira issue.

Details

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

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

Run ID: 01c115f4-6a93-4f48-a479-f05a3426d187

📥 Commits

Reviewing files that changed from the base of the PR and between 541574f and 66f6ccc.

⛔ 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

🚧 Files skipped from review as they are similar to previous changes (1)

• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml

---

Walkthrough

The scheduled test ocp-e2e-serial-ovn-techpreview-remote-s2s-libvirt-multi-p-p in the multiarch nightly 5.0 CI config now runs on Friday instead of Saturday.

Changes

CI Schedule Update

Layer / File(s)	Summary
Cron day shift ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml	Updates the scheduled test cron from 0 13 * * 6 to 0 13 * * 5 for ocp-e2e-serial-ovn-techpreview-remote-s2s-libvirt-multi-p-p.

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

Suggested reviewers: jordigilh, chadcrum

🚥 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 change: it updates the cron timing for the 5.0 TechPreviewNoUpgrade serial ppc64le job.
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	Diff only changes cron values in two YAML configs; no Ginkgo test titles or names were added or modified.
Test Structure And Quality	✅ Passed	Only CI cron YAML changed; no Ginkgo test code, so the test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	PASS: PR only adjusts a ci-operator cron schedule in YAML; it adds no Ginkgo tests or API usage to review, so MicroShift compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only a cron day change in ci-operator YAMLs; no Ginkgo tests or node-topology assumptions were added or modified.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only changes a periodic job cron in CI config; no deployment manifests, controllers, or scheduling/topology constraints were modified.
Ote Binary Stdout Contract	✅ Passed	Only CI cron YAML changed; no OTE binary code or stdout/logging paths were modified.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only the cron for an existing periodic job changed (0 13 * * 6 -> 0 13 * * 5); no Ginkgo tests or network logic were added.
No-Weak-Crypto	✅ Passed	PR only changes a cron day in two YAML job definitions; no crypto primitives, custom crypto, or secret comparisons were added.
Container-Privileges	✅ Passed	Only cron timings changed in the 5.0 periodic/job configs; no privileged, host*, SYS_ADMIN, or securityContext fields were added.
No-Sensitive-Data-In-Logs	✅ Passed	Only cron timing changed for one periodic job; no new log statements or sensitive data exposure appears in the touched files.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-merge-bot]

@KeerthanaAP, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: invalid ci-operator config: invalid configuration: tests: found duplicated test: (ocp-e2e-serial-ovn-techpreview-remote-s2s-libvirt-multi-p-p)

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-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: KeerthanaAP

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:

• ci-operator/config/openshift/multiarch/OWNERS [KeerthanaAP]
• ci-operator/jobs/openshift/multiarch/OWNERS [KeerthanaAP]

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]
@KeerthanaAP: 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-serial-ovn-techpreview-remote-s2s-libvirt-multi-p-p	N/A	periodic	Ci-operator config 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.

[openshift-ci]

@KeerthanaAP: 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.