ROX-21457: Disable daily ibmcloudz periodic tests

[janisz]

• Disable daily ibmcloudz periodic tests (daily-ibmcloudz-lts-qa-e2e-tests and daily-ibmcloudz-latest-qa-e2e-tests) by setting cron to 0 0 31 2 * (Feb 31 never fires)
• ibmcloudz cluster creation has been persistently failing
• Removing test entries would also require removing the ibmcloudz base image and the on-demand presubmit variants. Reverting that removal later is error-prone because make update regenerates job files - a simple git revert may not cleanly apply. Changing the cron makes re-enabling trivial: restore the original schedule.
• The determinize-ci-operator tool strips YAML comments during make update, so inline comments cannot survive the config normalization pipeline.

Summary by CodeRabbit

This PR disables the daily periodic test executions for IBM Cloud Z cluster E2E tests in the StackRox repository's OpenShift CI infrastructure. The change modifies the cron schedules for two periodic jobs: daily-ibmcloudz-lts-qa-e2e-tests and daily-ibmcloudz-latest-qa-e2e-tests, setting both to 0 0 31 2 * — a cron expression that will never trigger since February 31st does not exist.

The goal is to stop the recurring generation of Jira issues caused by persistent failures in ibmcloudz cluster creation that were being triggered by the daily automated test execution. The change effectively pauses these tests while the underlying infrastructure issues are addressed.

All other job configurations remain unchanged — test parameters and workflow references are preserved; only the cron scheduling mechanism is disabled.

[openshift-ci-robot]

@janisz: This pull request references ROX-21457 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Set cron to Feb 31 (never fires) to stop daily Jira spam from persistent ibmcloudz cluster creation failures.

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]

Walkthrough

Two cron schedule fields in the CI operator config for stackrox-stackrox-master are changed from active weekday expressions to 0 0 31 2 * for daily-ibmcloudz-lts-qa-e2e-tests and daily-ibmcloudz-latest-qa-e2e-tests. All other job configuration (env vars, workflow) remains unchanged.

Changes

IBM Cloud Z E2E cron schedule update

Layer / File(s)	Summary
Set impossible cron to disable IBM Cloud Z E2E jobs ci-operator/config/stackrox/stackrox/stackrox-stackrox-master.yaml	Cron fields for daily-ibmcloudz-lts-qa-e2e-tests and daily-ibmcloudz-latest-qa-e2e-tests are replaced with 0 0 31 2 *, a schedule that never triggers (February 31 does not exist).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'ROX-21457: Disable daily ibmcloudz periodic tests' directly and clearly describes the main change: disabling daily periodic tests for ibmcloudz by modifying cron schedules to an impossible date.
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 CI configuration files (YAML) and utility tools, not Ginkgo test code. The check for stable test names is inapplicable.
Test Structure And Quality	✅ Passed	PR modifies only CI configuration (YAML), not Ginkgo test code. Custom check for test structure/quality is not applicable to non-test-code changes.
Microshift Test Compatibility	✅ Passed	PR only modifies CI configuration (cron schedules), not test code. No new Ginkgo e2e tests are added, so MicroShift test compatibility check does not apply.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only modifies CI operator configuration (cron schedules), not test code. The SNO compatibility check applies only when new Ginkgo e2e tests are added, which is not the case here.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR modifies only a CI Operator configuration file's cron schedule. It introduces no deployment manifests, operator code, controllers, or any Kubernetes scheduling constraints that would affect...
Ote Binary Stdout Contract	✅ Passed	PR only modifies CI job scheduling in YAML config; check applies only to source/test code that produces stdout. No applicable code touched.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only modifies CI cron scheduling for existing tests in a YAML configuration file; no new Ginkgo e2e tests are added, so the IPv6/disconnected network compatibility check is not applicable.
No-Weak-Crypto	✅ Passed	PR modifies only a YAML CI/CD configuration file with cron schedule changes. No cryptographic code, algorithms, or implementations present; no weak crypto patterns found.
Container-Privileges	✅ Passed	File is a CI operator config, not a K8s/container manifest. Contains no privileged settings (privileged: true, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or securityContext).
No-Sensitive-Data-In-Logs	✅ Passed	The PR modifies cron schedules in a CI config file without introducing any logging statements or exposing passwords, tokens, API keys, PII, or other sensitive data.
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

---

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 and usage tips.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@janisz: 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-stackrox-stackrox-master-daily-ibmcloudz-latest-qa-e2e-tests	N/A	periodic	Ci-operator config changed
periodic-ci-stackrox-stackrox-master-daily-ibmcloudz-lts-qa-e2e-tests	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.

[openshift-ci]

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

[davdhacs]

/pj-rehearse ack

[openshift-merge-bot]

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

[davdhacs]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: davdhacs, janisz, jdao-rh

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/stackrox/OWNERS [davdhacs,janisz]
• ci-operator/jobs/stackrox/stackrox/OWNERS [davdhacs,janisz]

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