PERFSCALE: Shift 5.1 cron schedules to avoid conflicts with 5.0 - #83127
Conversation
The 5.1 PerfScale CI configs were cut from 5.0 and inherited identical cron schedules, causing resource contention on the shared aws-perfscale profile. This shifts all 24 cron entries in the 4 OCP PerfScale 5.1 config files: High-priority 120/252-node jobs (aws-perfscale profile): - Shifted to different days to prevent capacity conflicts - Added 30-minute time offsets as additional safety margin Standard jobs: - Weekly jobs shifted to alternate days of the week - Monthly day-of-month jobs shifted by +1 day - All jobs get +20 or +30 minute offsets for unique start times Run frequency is preserved (same number of runs per week/month). Generated periodics regenerated via make jobs. Signed-off-by: Chai Bot <ship-help-github@redhat.com>
WalkthroughThe PR updates cron schedules for 23 existing perfscale jobs across AWS loaded-upgrade, AWS nightly, metal nightly, and ROSA nightly configurations. ChangesPerfscale schedule updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 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 |
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-eng/ocp-perfscale/openshift-eng-ocp-perfscale-main__aws-5.1-nightly-x86.yaml`:
- Line 79: Update the cron schedule for control-plane-120nodes to run on four
weekdays by adding a day other than Sunday, Tuesday, Thursday, or Saturday,
while preserving the existing Monday, Wednesday, and Friday runs.
🪄 Autofix
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: Pro Plus
Run ID: ddaef4b6-fa2e-43fc-91ef-fc0f85ca15de
⛔ Files ignored due to path filters (1)
ci-operator/jobs/openshift-eng/ocp-perfscale/openshift-eng-ocp-perfscale-main-periodics.yamlis excluded by!ci-operator/jobs/**
📒 Files selected for processing (4)
ci-operator/config/openshift-eng/ocp-perfscale/openshift-eng-ocp-perfscale-main__aws-5.1-nightly-x86-loaded-upgrade-from-4.22.yamlci-operator/config/openshift-eng/ocp-perfscale/openshift-eng-ocp-perfscale-main__aws-5.1-nightly-x86.yamlci-operator/config/openshift-eng/ocp-perfscale/openshift-eng-ocp-perfscale-main__metal-5.1-nightly-x86.yamlci-operator/config/openshift-eng/ocp-perfscale/openshift-eng-ocp-perfscale-main__rosa-5.1-nightly-x86.yaml
|
@redhat-chai-bot: |
|
/pj-rehearse AI-generated. Review for accuracy. |
|
@redhat-chai-bot: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
All 5 rehearsal failures are expected — they're failing with This PR only changes Needs AI-generated. Review for accuracy. |
|
/pj-rehearse ack |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afcollins, redhat-chai-bot The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@afcollins: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@redhat-chai-bot: The following tests 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. |
9953401
into
openshift:main
…shift#83127) The 5.1 PerfScale CI configs were cut from 5.0 and inherited identical cron schedules, causing resource contention on the shared aws-perfscale profile. This shifts all 24 cron entries in the 4 OCP PerfScale 5.1 config files: High-priority 120/252-node jobs (aws-perfscale profile): - Shifted to different days to prevent capacity conflicts - Added 30-minute time offsets as additional safety margin Standard jobs: - Weekly jobs shifted to alternate days of the week - Monthly day-of-month jobs shifted by +1 day - All jobs get +20 or +30 minute offsets for unique start times Run frequency is preserved (same number of runs per week/month). Generated periodics regenerated via make jobs. Signed-off-by: Chai Bot <ship-help-github@redhat.com>
…shift#83127) The 5.1 PerfScale CI configs were cut from 5.0 and inherited identical cron schedules, causing resource contention on the shared aws-perfscale profile. This shifts all 24 cron entries in the 4 OCP PerfScale 5.1 config files: High-priority 120/252-node jobs (aws-perfscale profile): - Shifted to different days to prevent capacity conflicts - Added 30-minute time offsets as additional safety margin Standard jobs: - Weekly jobs shifted to alternate days of the week - Monthly day-of-month jobs shifted by +1 day - All jobs get +20 or +30 minute offsets for unique start times Run frequency is preserved (same number of runs per week/month). Generated periodics regenerated via make jobs. Signed-off-by: Chai Bot <ship-help-github@redhat.com>
Summary
Shift all cron schedules in the 4 OCP PerfScale 5.1 ci-operator config files so they no longer collide with the corresponding 5.0 jobs. The 5.1 configs were cut from 5.0 and had 100% identical cron schedules.
Changes
24 cron entries shifted across 4 config files + regenerated periodics.
Strategy
High-priority jobs (120/252-node, aws-perfscale profile)
AI-generated. Review for accuracy.
@afcollins requested in Slack thread
Summary by CodeRabbit