Skip to content

PERFSCALE: Shift 5.1 cron schedules to avoid conflicts with 5.0 - #83127

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
redhat-chai-bot:perfscale-5.1-cron-shift
Aug 7, 2026
Merged

PERFSCALE: Shift 5.1 cron schedules to avoid conflicts with 5.0#83127
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
redhat-chai-bot:perfscale-5.1-cron-shift

Conversation

@redhat-chai-bot

@redhat-chai-bot redhat-chai-bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

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

  • 120/252-node jobs (aws-perfscale profile): Shifted to completely different days to avoid resource contention
  • All other jobs: Shifted by +20-30 minutes and/or to alternate days of the week/month
  • Frequency preserved: Same number of runs per period, only timing changed
  • Yearly-scheduled jobs: Left unchanged (effectively disabled)

High-priority jobs (120/252-node, aws-perfscale profile)

Job 5.0 Days 5.1 Days Overlap
control-plane-120nodes Sun,Tue,Thu,Sat Mon,Wed,Fri None
control-plane-252nodes Mon Wed None
control-plane-ipsec-120nodes 11th,23rd 12th,24th None
control-plane-ipsec-252nodes 11th,23rd 12th,24th None
loaded-upgrade-120nodes 27th 28th None
loaded-upgrade-252nodes 26th 25th None

AI-generated. Review for accuracy.

@afcollins requested in Slack thread

Summary by CodeRabbit

  • Updated 24 cron schedules in four OpenShift CI PerfScale 5.1 configurations.
  • Shifted 5.1 jobs to avoid schedule collisions and resource contention with corresponding 5.0 jobs.
  • Preserved job frequency by using alternate days and 20–30 minute offsets.
  • Applied different schedule days to high-priority 120-node and 252-node jobs.
  • Regenerated the related periodic job definitions.
  • Left yearly jobs unchanged.

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>
@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

The PR updates cron schedules for 23 existing perfscale jobs across AWS loaded-upgrade, AWS nightly, metal nightly, and ROSA nightly configurations.

Changes

Perfscale schedule updates

Layer / File(s) Summary
AWS loaded-upgrade schedules
ci-operator/config/openshift-eng/ocp-perfscale/*loaded-upgrade-from-4.22.yaml
Three loaded-upgrade jobs receive new execution times and calendar dates.
AWS nightly schedules
ci-operator/config/openshift-eng/ocp-perfscale/*aws-5.1-nightly-x86.yaml
Seventeen AWS nightly jobs receive updated execution times and scheduled weekdays or month days.
Metal and ROSA nightly schedules
ci-operator/config/openshift-eng/ocp-perfscale/*metal-5.1-nightly-x86.yaml, ci-operator/config/openshift-eng/ocp-perfscale/*rosa-5.1-nightly-x86.yaml
Two metal jobs and one ROSA job receive updated cron schedules.

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

Possibly related PRs

  • openshift/release#83050: Modifies the same OCP perfscale 5.1 CI configuration files and adds related job configurations.

Suggested reviewers: deepsm007

🚥 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 and concisely describes the main change: shifting OCP PerfScale 5.1 cron schedules to avoid conflicts with 5.0 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 cron fields in four config files and regenerated periodics; no Ginkgo test declarations or test titles were added or modified.
Test Structure And Quality ✅ Passed The pull request changes only cron fields in four YAML configs and one generated periodics YAML; no Ginkgo test code or test setup, waits, or assertions changed.
Microshift Test Compatibility ✅ Passed The pull request changes only YAML cron fields in four configs and regenerated periodics; it adds no Ginkgo tests or MicroShift-relevant API references.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The verified PR diff changes only cron fields in four ci-operator YAML files; it adds no Ginkgo tests or test logic requiring SNO guards.
Topology-Aware Scheduling Compatibility ✅ Passed The PR changes only CI cron fields in four ci-operator config files and regenerated periodics; it adds no deployment manifests, operator code, controllers, replicas, or topology constraints.
Ote Binary Stdout Contract ✅ Passed The PR changes only cron fields in five YAML files. It adds no Go or OTE process-level code, so it introduces no stdout contract violation.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR changes only cron fields in five YAML configuration files; no new Ginkgo tests, IPv4 assumptions, or external connectivity were added.
No-Weak-Crypto ✅ Passed The HEAD^..HEAD diff contains only cron-field changes in YAML configs and generated periodics; no MD5, SHA1, DES, RC4, Blowfish, ECB, custom crypto, or secret comparisons were added.
Container-Privileges ✅ Passed The PR changes only cron fields in four configs and regenerated periodics. The patch adds no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs ✅ Passed The commit changes only cron expressions in four configs and regenerated periodics; no logging code or added passwords, tokens, API keys, PII, hostnames, or customer data appears.
✨ 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

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

@openshift-ci
openshift-ci Bot requested review from deepsm007 and droslean August 7, 2026 19:14
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 7, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between ccfd628 and 0d27409.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift-eng/ocp-perfscale/openshift-eng-ocp-perfscale-main-periodics.yaml is 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.yaml
  • ci-operator/config/openshift-eng/ocp-perfscale/openshift-eng-ocp-perfscale-main__aws-5.1-nightly-x86.yaml
  • ci-operator/config/openshift-eng/ocp-perfscale/openshift-eng-ocp-perfscale-main__metal-5.1-nightly-x86.yaml
  • ci-operator/config/openshift-eng/ocp-perfscale/openshift-eng-ocp-perfscale-main__rosa-5.1-nightly-x86.yaml

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@redhat-chai-bot: pj-rehearse could not automatically process this event because the request waited in queue for longer than 5 minutes. Use /pj-rehearse to trigger rehearsals manually.

@redhat-chai-bot

Copy link
Copy Markdown
Contributor Author

/pj-rehearse


AI-generated. Review for accuracy.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@redhat-chai-bot

Copy link
Copy Markdown
Contributor Author

All 5 rehearsal failures are expected — they're failing with failed to resolve release latest: server responded with 404: no tags exist within the release that satisfy the request because the 5.1.0-0.nightly release stream doesn't have any payloads yet (the 5.1 configs were just cut).

This PR only changes cron: fields — all 15 core CI checks (ci-operator-config, generated-config, prow-config-semantics, yamllint, etc.) are passing. The rehearsal failures are unrelated to the cron schedule changes.

Needs rehearsals-ack + /lgtm from a PerfScale reviewer to merge.


AI-generated. Review for accuracy.

@afcollins afcollins left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 7, 2026
@afcollins

Copy link
Copy Markdown
Contributor

/pj-rehearse ack

@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

[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

Details Needs approval from an approver in each of these files:

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

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 7, 2026
@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@redhat-chai-bot: 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-eng-ocp-perfscale-main-aws-5.1-nightly-x86-loaded-upgrade-from-4.22-loaded-upgrade-252nodes 0d27409 link unknown /pj-rehearse periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.1-nightly-x86-loaded-upgrade-from-4.22-loaded-upgrade-252nodes
ci/rehearse/periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.1-nightly-x86-control-plane-etcdencrypt-24nodes 0d27409 link unknown /pj-rehearse periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.1-nightly-x86-control-plane-etcdencrypt-24nodes
ci/rehearse/periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.1-nightly-x86-control-plane-120nodes 0d27409 link unknown /pj-rehearse periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.1-nightly-x86-control-plane-120nodes
ci/rehearse/periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.1-nightly-x86-control-plane-252nodes 0d27409 link unknown /pj-rehearse periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.1-nightly-x86-control-plane-252nodes
ci/rehearse/periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.1-nightly-x86-control-plane-ipsec-120nodes 0d27409 link unknown /pj-rehearse periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.1-nightly-x86-control-plane-ipsec-120nodes

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.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 9953401 into openshift:main Aug 7, 2026
16 of 21 checks passed
TimurMP pushed a commit to TimurMP/release that referenced this pull request Aug 9, 2026
…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>
jzding pushed a commit to jzding/release that referenced this pull request Aug 11, 2026
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants