NO-ISSUE: Temporary disable of 5.0 release periodics in ushift

[pacevedom]

Summary by CodeRabbit

• Temporarily limits six MicroShift 5.0 release periodic jobs to June.
• Preserves their Sunday, Tuesday, and Thursday schedules at 03:00.
• Prevents these release jobs from running during other months.

[openshift-ci-robot]

@pacevedom: This pull request explicitly references no 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: Pro Plus

Run ID: b1874ab2-ad6f-4330-af8b-3c49dc4c878d

📥 Commits

Reviewing files that changed from the base of the PR and between b136251 and e06ffce.

⛔ Files ignored due to path filters (1)

• ci-operator/jobs/openshift/microshift/openshift-microshift-release-5.0-periodics.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (1)

• ci-operator/config/openshift/microshift/openshift-microshift-release-5.0__periodics.yaml

---

Walkthrough

The change restricts six MicroShift release periodic jobs to June. Their Sunday, Tuesday, and Thursday execution times remain at 03:00.

Changes

MicroShift release schedules

Layer / File(s)	Summary
Restrict release jobs to June ci-operator/config/openshift/microshift/openshift-microshift-release-5.0__periodics.yaml	The six AWS and Bootc release periodic jobs now run in June only. Their existing Sunday, Tuesday, and Thursday schedules at 03:00 remain unchanged.

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

Possibly related PRs

• openshift/release#83127: Updates cron schedules for a different set of CI periodic jobs.

Suggested reviewers: fracappa, ggiguash

🚥 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 the temporary disabling of MicroShift 5.0 release periodic jobs, which matches the main change.
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 commit changes only two CI YAML cron configurations and adds no Ginkgo test titles or dynamic test-name values.
Test Structure And Quality	✅ Passed	The pull request changes only cron fields in two YAML job definitions; it adds no Ginkgo test code, so the listed test-quality requirements are not applicable.
Microshift Test Compatibility	✅ Passed	The commit changes only two YAML periodic-job files and six cron expressions; it adds no Ginkgo e2e tests or new MicroShift-incompatible API usage.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The patch changes only six cron values in two YAML configuration files; it adds no Ginkgo tests or multi-node assumptions, so the SNO check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	The diff changes only six cron expressions in two CI YAML files; it adds no deployment, operator, controller, or topology scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The pull request changes only cron fields in two YAML files; no OTE binary, suite setup, or process-level stdout write is added.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The patch changes only cron fields in two YAML files and adds no Ginkgo e2e tests or network connectivity.
No-Weak-Crypto	✅ Passed	The commit changes only six cron fields in two YAML files; added lines contain no MD5, SHA1, DES, RC4, Blowfish, ECB, crypto API, secret, token, or comparison usage.
Container-Privileges	✅ Passed	The commit changes only six cron fields in two periodic YAML files; no changed or existing entries set privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation.
No-Sensitive-Data-In-Logs	✅ Passed	The diff changes only 12 cron values from * to 6; it adds no logging, credentials, tokens, PII, hostnames, or customer data.

✨ 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-merge-bot]

[REHEARSALNOTIFIER]
@pacevedom: 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-microshift-release-5.0-periodics-e2e-aws-tests-bootc-release-periodic-el10	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-microshift-release-5.0-periodics-e2e-aws-tests-bootc-release-periodic-el9	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-microshift-release-5.0-periodics-e2e-aws-tests-release-arm-periodic	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-microshift-release-5.0-periodics-e2e-aws-tests-release-periodic	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-microshift-release-5.0-periodics-e2e-aws-tests-bootc-release-arm-periodic-el10	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-microshift-release-5.0-periodics-e2e-aws-tests-bootc-release-arm-periodic-el9	N/A	periodic	Ci-operator config changed

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.

[ggiguash]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom

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/microshift/OWNERS [ggiguash,pacevedom]
• ci-operator/jobs/openshift/microshift/OWNERS [ggiguash,pacevedom]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ggiguash]

/pj-rehearse ack

[openshift-merge-bot]

@ggiguash: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

[ggiguash]

/pj-rehearse ack

[openshift-merge-bot]

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

[openshift-ci]

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