Skip to content

NO-ISSUE: Disable 5.1 ushift periodics - #83246

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
pacevedom:disable-5.1-ushift
Aug 11, 2026
Merged

NO-ISSUE: Disable 5.1 ushift periodics#83246
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
pacevedom:disable-5.1-ushift

Conversation

@pacevedom

@pacevedom pacevedom commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Disables recurring MicroShift 5.1 periodic jobs in openshift/release by restricting their schedules to June 6.
  • Preserves the existing execution times and weekday filters for weekly and release periodic jobs.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 11, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@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

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

The MicroShift 5.1 periodic job schedules now run on June 6. Existing execution times and weekday filters remain unchanged.

Changes

MicroShift periodic schedules

Layer / File(s) Summary
Nightly schedule updates
ci-operator/config/openshift/microshift/openshift-microshift-release-5.1__periodics.yaml
Nightly jobs now use day-of-month 6 while retaining weekday filters and existing times.
Release schedule updates
ci-operator/config/openshift/microshift/openshift-microshift-release-5.1__periodics.yaml
Release periodic jobs now use day-of-month 6 while retaining Sunday, Tuesday, and Thursday filters and existing times.

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

Possibly related PRs

Suggested labels: lgtm, approved, rehearsals-ack

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 states that the 5.1 MicroShift periodic jobs are disabled.
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 schedules in two YAML job files; no Ginkgo test declarations or test titles were added or modified.
Test Structure And Quality ✅ Passed The commit changes only cron fields in two YAML files; it contains no Ginkgo test code, It blocks, setup/cleanup, cluster waits, or assertions to review.
Microshift Test Compatibility ✅ Passed The pull request changes only cron fields in two YAML files; it adds no Ginkgo tests, test code, or OpenShift API references to assess.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR changes only cron schedules in two YAML CI files; it adds no Ginkgo e2e tests or multi-node test assumptions.
Topology-Aware Scheduling Compatibility ✅ Passed The PR changes only CI periodic-job YAML files; all changed lines modify cron schedules, with no pod scheduling constraints, replicas, affinities, selectors, tolerations, or PDBs.
Ote Binary Stdout Contract ✅ Passed The pull request only changes MicroShift periodic-job YAML schedules; it adds no OTE binary or process-level stdout code.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The commit changes only cron fields in two periodic-job YAML files; it adds no Ginkgo tests or IPv4/external connectivity logic.
No-Weak-Crypto ✅ Passed The commit changes only cron field values in two YAML schedule files; no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, crypto implementation, or secret comparison was added.
Container-Privileges ✅ Passed Both changed files alter only cron fields; no forbidden privilege keys occur. Existing image setup uses USER 0 for package installation, then switches to USER 1000.
No-Sensitive-Data-In-Logs ✅ Passed The commit changes only cron schedule fields in the config and generated jobs files; it adds no logging statements or passwords, tokens, API keys, 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

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

@openshift-ci
openshift-ci Bot requested review from agullon and kasturinarra August 11, 2026 10:51
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 11, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[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.1-periodics-e2e-aws-tests-nightly N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-release-arm-periodic N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-bootc-c2cc-arm-nightly N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-bootc-release-arm-periodic-el10 N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-bootc-arm-nightly-el10 N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-clusterbot-nightly N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-footprint-and-performance-nightly N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-bootc-release-arm-periodic-el9 N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-ovn-ocp-conformance-serial N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-publish-release-notes N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-release-periodic N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-ai-model-serving-nightly N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-bootc-arm-nightly-el9 N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-bootc-release-periodic-el9 N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-bootc-nightly-el10 N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-arm-nightly N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-ovn-ocp-conformance N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-bootc-nightly-el9 N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-bootc-c2cc-nightly N/A periodic Ci-operator config changed
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-bootc-release-periodic-el10 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-microshift-release-5.1-periodics-e2e-aws-tests-cache-nightly-arm
periodic-ci-openshift-microshift-release-5.1-periodics-rebase-on-nightlies
periodic-ci-openshift-microshift-release-5.1-periodics-e2e-aws-tests-cache-nightly

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.

@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/microshift/openshift-microshift-release-5.1__periodics.yaml`:
- Line 56: Replace the changed periodic cron schedules, including the one shown
under the release scheduling configuration, with the repository’s
impossible-date parking pattern such as 0 4 31 2 *. Apply this consistently to
all changed schedules and run make update afterward.
🪄 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: 51fcb6d9-0b8d-459b-8afb-fb1eb351b373

📥 Commits

Reviewing files that changed from the base of the PR and between c91a2bb and c7ad32d.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/microshift/openshift-microshift-release-5.1-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (1)
  • ci-operator/config/openshift/microshift/openshift-microshift-release-5.1__periodics.yaml

- intranet
- nested-podman
cron: 0 4 * * 1-5
cron: 0 4 * 6 1-5

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.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -eu

file='ci-operator/config/openshift/microshift/openshift-microshift-release-5.1__periodics.yaml'

printf '%s\n' '--- target cron entries ---'
rg -n '^[[:space:]]+cron:' "$file"

printf '%s\n' '--- nearby job definitions ---'
sed -n '1,360p' "$file"

printf '%s\n' '--- repository parking schedules ---'
rg -n -i 'cron:|impossible|park|disable' ci-operator/config | rg -i 'cron:|impossible|park|disable' | head -200

printf '%s\n' '--- file status ---'
git status --short -- "$file"
git diff --stat -- "$file"

Repository: openshift/release

Length of output: 35442


🏁 Script executed:

#!/bin/bash
set -eu

file='ci-operator/config/openshift/microshift/openshift-microshift-release-5.1__periodics.yaml'

printf '%s\n' '--- target cron entries ---'
rg -n '^[[:space:]]+cron:' "$file"

printf '%s\n' '--- nearby job definitions ---'
sed -n '1,360p' "$file"

printf '%s\n' '--- repository parking schedules ---'
rg -n -i 'cron:|impossible|park|disable' ci-operator/config | head -200

printf '%s\n' '--- file status ---'
git status --short -- "$file"
git diff --stat -- "$file"

Repository: openshift/release

Length of output: 37752


🏁 Script executed:

#!/bin/bash
set -eu

file='ci-operator/config/openshift/microshift/openshift-microshift-release-5.1__periodics.yaml'

printf '%s\n' '--- parent revision cron entries ---'
git show "HEAD^:$file" | rg -n '^[[:space:]]+cron:' || true

printf '%s\n' '--- exact parent-to-current changes ---'
git diff --no-ext-diff --unified=3 HEAD^ -- "$file"

printf '%s\n' '--- nearby disabled-periodic examples ---'
for f in \
  ci-operator/config/psalajova/test/psalajova-test-master.yaml \
  ci-operator/config/insights-onprem/cost-onprem-chart/insights-onprem-cost-onprem-chart-main__periodics.yaml \
  ci-operator/config/rhbk/sso-test/rhbk-sso-test-main__rhsso-product-ocp4.19-lp-interop.yaml
do
  if test -f "$f"; then
    printf '\n--- %s ---\n' "$f"
    sed -n '1,120p' "$f"
  fi
done

Repository: openshift/release

Length of output: 19346


Use an impossible cron date to disable these periodics.

0 4 * 6 1-5 runs every weekday in June. The release schedules run every Sunday, Tuesday, and Thursday in June. Replace all changed schedules with the repository parking pattern, such as 0 4 31 2 *, and run make update.

🤖 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/microshift/openshift-microshift-release-5.1__periodics.yaml`
at line 56, Replace the changed periodic cron schedules, including the one shown
under the release scheduling configuration, with the repository’s
impossible-date parking pattern such as 0 4 31 2 *. Apply this consistently to
all changed schedules and run make update afterward.

Source: Learnings

@openshift-ci

openshift-ci Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

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

@ggiguash

Copy link
Copy Markdown
Contributor

/lgtm
/pj-rehearse ack

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

openshift-ci Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

[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:

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

@ggiguash: 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 11, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit da0b9b5 into openshift:main Aug 11, 2026
16 checks passed
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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.

3 participants