Update PowerVS CI cron schedules#81136
Conversation
|
Warning Review limit reached
More reviews will be available in 39 minutes and 3 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
WalkthroughThe nightly multiarch CI schedules for ChangesNightly multiarch cron updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Neha-dot-Yadav
force-pushed
the
powervs-5.0-cron-update
branch
from
e021c21 to
a58daa8
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.18.yaml`:
- Line 593: The cron schedule change in the openshift-multiarch nightly config
also requires regenerating the generated Prow job definitions. Update the
artifacts produced by make update so the corresponding entries under
ci-operator/jobs/ reflect the new schedule, and commit those generated changes
along with the config update.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: a32fa99f-ea19-4a36-8aaa-e6eeeb6f8cbf
📒 Files selected for processing (5)
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.18.yamlci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.19.yamlci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.21.yamlci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23.yamlci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
| capabilities: | ||
| - sshd-bastion | ||
| cron: 0 7 * * * | ||
| cron: 0 7 * * 1,3,5 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf 'Changed generated job files:\n'
git diff --name-only -- ci-operator/jobs
printf '\nUpdated config cron values:\n'
rg -n 'cron:' \
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.18.yaml \
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.19.yaml \
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.21.yaml \
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23.yaml \
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
printf '\nGenerated job entries touching this test name:\n'
rg -n -C2 'ocp-e2e-ovn-powervs-capi-multi-p-p|cron:' ci-operator/jobsRepository: openshift/release
Length of output: 50374
Run make update to regenerate Prow jobs for the cron change.
Modifying the cron schedule in ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.18.yaml requires regenerating the corresponding job definitions in ci-operator/jobs/. The generated job files for this configuration are missing from the PR, so the new schedule will not be applied.
Execute make update to regenerate the artifacts and commit the resulting changes to ci-operator/jobs/.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.18.yaml`
at line 593, The cron schedule change in the openshift-multiarch nightly config
also requires regenerating the generated Prow job definitions. Update the
artifacts produced by make update so the corresponding entries under
ci-operator/jobs/ reflect the new schedule, and commit those generated changes
along with the config update.
Sources: Coding guidelines, Learnings
Neha-dot-Yadav
force-pushed
the
powervs-5.0-cron-update
branch
from
a58daa8 to
590f14e
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Neha-dot-Yadav The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Neha-dot-Yadav
force-pushed
the
powervs-5.0-cron-update
branch
from
590f14e to
45cf0fa
Compare
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@Neha-dot-Yadav: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
prb112
left a comment
prb112
left a comment
There was a problem hiding this comment.
Hey @Neha-dot-Yadav
I thought about having you change 5.0 PowerVS nightly from Mon/Wed/Fri once daily to twice daily to Change 5.0 PowerVS nightly from 5 days a week twice daily.
Let me explain - 5.0 is important, we should run as much as possible and move to twice daily.
4.23 should run a minimum right now. I think the schedule is fine.
Thanks
Paul
2 participants
Update PowerVS IPI nightly cron schedules for multiarch jobs to rebalance load across Dal10 and Lon04 regions.
Changes:
Change 4.18 PowerVS nightly from daily to Mon/Wed/Fri
Change 4.19 PowerVS nightly from daily to Sun/Tue/Thu
Change 4.21 PowerVS nightly from twice daily to once daily
Change 4.23 PowerVS nightly from 4 days/week to Tue/Thu/Sat
Change 5.0 PowerVS nightly from Mon/Wed/Fri once daily to twice daily
Keep 4.22 unchanged since it already matches the required twice-daily schedule
Updated schedules
Notes
Avoids the previous heavy-load 4.19 Dal10 slot at 0 15 * * *
Maintains at least 3 hours gap between jobs in the same region
Keeps 4.18 and 4.19 on alternating day sets
Summary by CodeRabbit
This PR updates OpenShift CI multi-arch configuration for PowerVS IPI nightly runs (in
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-*.yaml) by changing the cron schedules used by theocp-e2e-ovn-powervs-capi-multi-p-pjob. The new timing spreads workload more evenly across Dal10 and Lon04 regions, reduces peak contention, and preserves spacing between runs in the same region.Updated nightly schedules:
0 7 * * 1,3,5(instead of daily)0 1 * * 0,2,4(instead of0 15 * * *)0 10 * * *(reduced from twice daily to once daily)0 4,16 * * *(unchanged)0 10 * * 2,4,6(reduced from 4 days/week to Tue/Thu/Sat)0 16,22 * * *(increased from once daily to twice daily)Net effect: the rollout avoids the previously heavy-load 4.19 Dal10 slot at
0 15 * * *, keeps at least a ~3-hour gap between jobs targeting the same region, and maintains alternating day sets for 4.18 and 4.19.