CNTRLPLANE-3846: Multiple CI jobs failing for 5.0.

[amogh-redhat]

What this PR does / why we need it:
Multiple periodic CI jobs in the openshift/hypershift repository have been consistently failing across release 5.0 with near-zero pass rates, consuming significant CI infrastructure resources with no useful signal.

e2e-aws-ovn-proxy-conformance
e2e-ibmcloud-ovn-iks
e2e-ibmcloud-ovn-roks
e2e-powervs-ovn

I have updated the cron schedule to trigger once a year on 1st Dec every year (cron: 0 4 1 12 *) and for few jobs, changed the minimal interval to 3 months (2190d) so we get enough time to fix the errors and the jobs wont trigger till then.
The job definition itself stays in the configuration file, so the YAML remains syntactically valid.
If these jobs had presubmit/postsubmit triggers defined elsewhere (like running on PRs via /test jobname), those manual/PR triggers would still work.

Which issue(s) this PR fixes: Failing periodic jobs.

Fixes - https://redhat.atlassian.net/browse/CNTRLPLANE-3946

Special notes for your reviewer:

Checklist:
Subject and description added to both, commit and PR.
Relevant issues have been referenced.
This change includes docs.
This change includes unit tests.

[openshift-ci-robot]

@amogh-redhat: This pull request references CNTRLPLANE-3846 which is a valid jira issue.

Details

In response to this:

What this PR does / why we need it:
Multiple periodic CI jobs in the openshift/hypershift repository have been consistently failing across release 5.0 with near-zero pass rates, consuming significant CI infrastructure resources with no useful signal.

e2e-aws-ovn-proxy-conformance
e2e-ibmcloud-ovn-iks
e2e-ibmcloud-ovn-roks
e2e-powervs-ovn

I have updated the cron schedule to trigger once a year on 1st Dec every year (cron: 0 4 1 12 *) and for few jobs, changed the minimal interval to 3 months (2190d) so we get enough time to fix the errors and the jobs wont trigger till then.
The job definition itself stays in the configuration file, so the YAML remains syntactically valid.
If these jobs had presubmit/postsubmit triggers defined elsewhere (like running on PRs via /test jobname), those manual/PR triggers would still work.

Which issue(s) this PR fixes: Failing periodic jobs.

Fixes - https://redhat.atlassian.net/browse/CNTRLPLANE-3946

Special notes for your reviewer:

Checklist:
Subject and description added to both, commit and PR.
Relevant issues have been referenced.
This change includes docs.
This change includes unit tests.

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]

Warning

Review limit reached

@amogh-redhat, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 4df83241-1936-4a0f-8260-c971716029a7

📥 Commits

Reviewing files that changed from the base of the PR and between 5480392 and 3405e5a.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

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

---

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-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: amogh-redhat
Once this PR has been reviewed and has the lgtm label, please assign devguyio for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/hypershift/OWNERS
• ci-operator/jobs/openshift/hypershift/OWNERS

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]

[REHEARSALNOTIFIER]
@amogh-redhat: 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-hypershift-release-5.0-periodics-e2e-aws-ovn-proxy-conformance	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-powervs-ovn	N/A	periodic	Ci-operator config changed

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]

@amogh-redhat: 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.