NO-JIRA: Restore daily cron for 5.0 powervc and powervs-capi jobs

[Neha-dot-Yadav]

PR #82853 disabled the following jobs by setting cron to '0 0 1 1 *'
(once a year) due to 0% overall pass rate over 3 months:

• nightly-5.0-ocp-e2e-ovn-powervc-multi-p-p
• nightly-5.0-ocp-e2e-ovn-powervs-capi-multi-p-p

However, the 0% reflects testcase failures, not installation failures.
Installation was passing in 12/13 recent PowerVC runs and 9/15 PowerVS
runs. The overall job result is marked FAILURE when TCs fail, which
caused the bot to incorrectly treat these as fully broken jobs.

Restore original schedules:

• powervc: 0 12 * * * (daily at 12:00 UTC)
• powervs-capi: 0 9,21 * * * (twice daily at 09:00 and 21:00 UTC)"

Summary by CodeRabbit

Restores scheduled execution for two OpenShift 5.0 multi-architecture OVN end-to-end jobs:

• nightly-5.0-ocp-e2e-ovn-powervc-multi-p-p: daily at 12:00 UTC.
• nightly-5.0-ocp-e2e-ovn-powervs-capi-multi-p-p: daily at 09:00 and 21:00 UTC.

These schedules re-enable coverage for PowerVC and PowerVS installation validation.

[openshift-ci-robot]

@Neha-dot-Yadav: This pull request explicitly references no jira issue.

Details

In response to this:

PR #82853 disabled the following jobs by setting cron to '0 0 1 1 *'
(once a year) due to 0% overall pass rate over 3 months:

• nightly-5.0-ocp-e2e-ovn-powervc-multi-p-p
• nightly-5.0-ocp-e2e-ovn-powervs-capi-multi-p-p

However, the 0% reflects testcase failures, not installation failures.
Installation was passing in 12/13 recent PowerVC runs and 9/15 PowerVS
runs. The overall job result is marked FAILURE when TCs fail, which
caused the bot to incorrectly treat these as fully broken jobs.

Restore original schedules:

• powervc: 0 12 * * * (daily at 12:00 UTC)
• powervs-capi: 0 9,21 * * * (twice daily at 09:00 and 21:00 UTC)"

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: Pro Plus

Run ID: c4ee2ce2-d47f-4ac6-89b2-790fc0f3686a

📥 Commits

Reviewing files that changed from the base of the PR and between 8787b92 and febd422.

⛔ 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

The change updates two multi-architecture E2E test schedules from annual execution to daily or twice-daily execution.

Changes

Multi-architecture E2E schedules

Layer / File(s)	Summary
Update E2E cron schedules ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml	The PowerVC OVN job now runs daily at 12:00. The PowerVS CAPI job now runs daily at 09:00 and 21:00.

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

Possibly related PRs

• openshift/release#82853: Modifies cron schedules for multi-architecture test jobs in the same configuration.
• openshift/release#83054: Modifies nightly CI cron schedules in the multi-architecture configuration.

Suggested reviewers: ibm-adarsh, redhat-chai-bot, prb112

🚥 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 describes restoring recurring cron schedules for the 5.0 PowerVC and PowerVS CAPI jobs.
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	The PR changes only two cron schedules in the config and generated periodics YAML; it adds no Ginkgo test titles or dynamic test-name values.
Test Structure And Quality	✅ Passed	The commit changes only two YAML configuration files for cron schedules; no Ginkgo source or Ginkgo markers are present, so this test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	The commit changes only two YAML cron fields and generated periodic-job configuration; it adds no Ginkgo e2e tests or MicroShift-incompatible test code.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The pull request changes only cron fields in two YAML configuration files; it adds no Ginkgo e2e tests that require SNO compatibility review.
Topology-Aware Scheduling Compatibility	✅ Passed	The PR changes only CI cron fields in two YAML configuration/job files; it adds no deployment manifests, operator code, controllers, or topology-dependent pod scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The commit changes only two YAML cron fields and adds no OTE binary or process-level stdout code.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The PR changes only two cron fields and their generated job entries; it adds no Ginkgo tests or external network usage to assess.
No-Weak-Crypto	✅ Passed	The PR changes only two YAML cron values; the complete commit diff contains no crypto primitive, weak algorithm, custom crypto, or secret-comparison code.
Container-Privileges	✅ Passed	The PR changes only two cron fields in the source and generated ProwJob YAML; no changed content adds privileged, host namespace, SYS_ADMIN, escalation, or root settings.
No-Sensitive-Data-In-Logs	✅ Passed	The commit changes only four cron fields in two YAML files; no logging statements or newly exposed passwords, tokens, PII, hostnames, or customer data were added.

✨ 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: Neha-dot-Yadav
Once this PR has been reviewed and has the lgtm label, please assign rvanderp3 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]
@Neha-dot-Yadav: 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-powervs-capi-multi-p-p	N/A	periodic	Ci-operator config changed

The following jobs are not rehearsable without the network-access-rehearsals-ok, and approved labels present on this PR. This is due to the restrict_network_access field being set to false. The network-access-rehearsals-ok label can be added by any openshift org member other than the PR's author by commenting: /pj-rehearse network-access-allowed:

Test name
periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-e2e-ovn-powervc-multi-p-p

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

@Neha-dot-Yadav: 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.