no-jira: revert: lower frequency of 4.22 all-regions jobs

[tthvo]

This reverts commit 32eaaf1.

Background: Previously, we bumped the frequency of these jobs to 4 times per day to accelerate test result collection. As of now, we have enough data so let's lower the frequency to as before.

Summary by CodeRabbit

This pull request reverts the OpenShift 4.22 nightly verification tests back to daily execution schedules for three all-regions installation jobs.

Changes Made:

The PR modifies three cron schedules in the OpenShift verification-tests CI configuration for 4.22 nightly releases:

1. azure-ipi-all-regions-f1: Reverted from running 4 times per day (0,6,12,18 hours) to once daily at 04:02 UTC
2. gcp-ipi-all-regions-f1: Reverted from running 4 times per day (0,6,12,18 hours) to once daily at 17:44 UTC
3. gcp-ipi-all-regions-without-storage-test-f2: Reverted from running 4 times per day (0,6,12,18 hours) to once on odd-numbered days at 13:39 UTC

Context:

These all-regions test jobs validate OpenShift installation across multiple cloud regions and instance types. The previous increase to 4x daily execution was a temporary measure to accelerate test data collection during an earlier phase. Now that sufficient test coverage has been achieved, the execution frequency is being normalized back to the standard daily schedule to reduce infrastructure load and operational overhead.

[openshift-ci-robot]

@tthvo: This pull request explicitly references no jira issue.

Details

In response to this:

This reverts commit 32eaaf1.

Background: Previously, we bumped the frequency of these jobs to 4 times per day to accelerate test result collection. As of now, we have enough data so let's lower the frequency to normal daily.

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.

[tthvo]

/hold

[coderabbitai]

Walkthrough

Three cron schedule fields in the 4.22 nightly installation config are updated: azure-ipi-all-regions-f1 switches from 0,6,12,18 hours to hour 4; gcp-ipi-all-regions-f1 switches to hour 17; gcp-ipi-all-regions-without-storage-test-f2 switches to minute 39, hour 13, on odd days of the month.

Changes

Nightly 4.22 Job Cron Schedules

Layer / File(s)	Summary
Cron expression updates for three nightly jobs ci-operator/config/openshift/verification-tests/openshift-verification-tests-main__installation-nightly-4.22.yaml	azure-ipi-all-regions-f1 cron changed to 0 4 * * *; gcp-ipi-all-regions-f1 changed to 0 17 * * *; gcp-ipi-all-regions-without-storage-test-f2 changed to 39 13 1,3,5,...,29 * *. No other job fields are modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
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	This PR modifies only CI job scheduling (cron expressions) in a YAML configuration file. It does not modify any Ginkgo test names (It(), Describe(), Context(), etc.), so the custom check for stable...
Test Structure And Quality	✅ Passed	Custom check for Ginkgo test code quality is not applicable; PR only modifies YAML configuration files for CI job scheduling, not test code.
Microshift Test Compatibility	✅ Passed	No new Ginkgo e2e tests were added in this PR. The changes only modify cron schedules in a CI configuration YAML file, which is outside the scope of the MicroShift compatibility check.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only modifies CI configuration YAML files and does not add any new Ginkgo e2e tests. The check specifically applies to new test code, not configuration changes.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR modifies CI test job cron schedules only, not deployment manifests or pod scheduling constraints. The topology-aware scheduling check is not applicable to CI configuration files.
Ote Binary Stdout Contract	✅ Passed	PR only modifies YAML CI configuration cron schedules, not source code. Custom check for OTE Binary Stdout Contract violations is inapplicable to non-code files.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies only CI job cron schedules in YAML config file; no new Ginkgo e2e tests are added, so the IPv6/disconnected network compatibility check does not apply.
No-Weak-Crypto	✅ Passed	This PR modifies only a CI/CD test job scheduling configuration file (YAML). No cryptographic code, weak cipher implementations, custom crypto, or secret comparison logic exists in the changes. The...
Container-Privileges	✅ Passed	This PR modifies cron schedules in a CI operator configuration file, not Kubernetes container manifests. No privileged container configurations, hostPID, hostNetwork, hostIPC, SYS_ADMIN capabilitie...
No-Sensitive-Data-In-Logs	✅ Passed	PR contains only cron schedule configuration changes in a YAML file with no logging logic, code changes, or sensitive data exposure.
Title check	✅ Passed	The title accurately describes the main change: reverting the frequency of 4.22 all-regions jobs to daily execution, matching the actual cron schedule updates in the changeset.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@tthvo: 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-verification-tests-main-installation-nightly-4.22-gcp-ipi-all-regions-without-storage-test-f2	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-verification-tests-main-installation-nightly-4.22-azure-ipi-all-regions-f1	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-verification-tests-main-installation-nightly-4.22-gcp-ipi-all-regions-f1	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.

[coderabbitai]

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/verification-tests/openshift-verification-tests-main__installation-nightly-4.22.yaml`:
- Line 1137: The cron expression at line 1137 is configured to run only on odd
days of the month (using the day-of-month field
`1,3,5,7,9,11,13,15,17,19,21,23,25,27,29`), not daily. To align with the PR goal
of reverting to daily execution, modify the cron value from `39 13
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29 * *` to `39 13 * * *` which will execute
the job daily at 13:39 UTC regardless of which day of the month it is.

🪄 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: a17efe3c-b80d-4fe3-8b5f-0dac3ddf6cb9

📥 Commits

Reviewing files that changed from the base of the PR and between 3736154 and 141da7b.

⛔ Files ignored due to path filters (1)

• ci-operator/jobs/openshift/verification-tests/openshift-verification-tests-main-periodics.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (1)

• ci-operator/config/openshift/verification-tests/openshift-verification-tests-main__installation-nightly-4.22.yaml

[openshift-ci]

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

[tthvo]

/pj-rehearse ack

[openshift-merge-bot]

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

[pruan-rht]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pruan-rht, tthvo

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/verification-tests/OWNERS [pruan-rht]
• ci-operator/jobs/openshift/verification-tests/OWNERS [pruan-rht]

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

[tthvo]

I'm holding so we can get a few more runs over the weekends :D Will cancel hold on Monday 👍