Change e2e-aws-ovn-conformance-techpreview to run daily for hypershift

[jsafrane]

OpenShift feature gate promotion criteria require CI jobs on "required platforms" to run 7 times / week. HyperShift is a reqired platform. So we need to run the techpreview job daily.

Summary by CodeRabbit

The PR changes the HyperShift CI configuration for OpenShift 5.0 and 5.1. It schedules the e2e-aws-ovn-conformance-techpreview periodic job to run daily instead of weekly. This provides seven weekly runs on the required HyperShift platform.

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

Run ID: 57ce3836-9b23-491f-904c-46b3246a8844

📥 Commits

Reviewing files that changed from the base of the PR and between 46c71d1 and af9a760.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (2)

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

---

Walkthrough

The e2e-aws-ovn-conformance-techpreview periodic job now runs daily for HyperShift release 5.0 and 5.1 configurations.

Changes

OVN conformance schedule

Layer / File(s)	Summary
Daily OVN conformance schedule ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml, ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.1__periodics.yaml	The e2e-aws-ovn-conformance-techpreview job changes from weekly to daily execution for both release configurations.

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

Possibly related PRs

• openshift/release#83054: Changes CI job schedules from less frequent execution in different job configurations.
• openshift/release#83092: Changes periodic CI job schedules from weekly to daily in different configurations.

Suggested reviewers: mgencur, jparrill

🚥 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 and concisely describes changing the HyperShift conformance job to run daily.
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 periodic cron schedules; no Ginkgo test titles or dynamic test-name expressions are added or modified.
Test Structure And Quality	✅ Passed	The PR modifies only CI job configuration YAML files to change periodic job schedules. It contains no Ginkgo test code or test structure changes, making the test quality review check inapplicable.
Microshift Test Compatibility	✅ Passed	The commit only changes periodic YAML cron schedules from weekly to daily; it adds no Ginkgo tests or test declarations requiring MicroShift compatibility review.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The commit adds no Ginkgo tests or Go files; it only changes HyperShift periodic job cron schedules to daily.
Topology-Aware Scheduling Compatibility	✅ Passed	The diff only changes Prow periodic cron values in four CI YAML files; it adds no deployment, controller, replica, affinity, selector, spread, taint, or PDB constraints.
Ote Binary Stdout Contract	✅ Passed	The commit changes only four YAML cron fields; no OTE binary, suite setup, logging, or stdout-writing code was added.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The pull request changes only four YAML schedule entries from weekly to daily; it adds no Ginkgo e2e tests or networking code to assess.
No-Weak-Crypto	✅ Passed	The PR diff adds only cron schedule values in four periodic-job YAML files. It adds no weak-crypto algorithm, custom crypto code, or secret/token comparison.
Container-Privileges	✅ Passed	The PR changes only cron schedules. The complete diff adds no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root settings.
No-Sensitive-Data-In-Logs	✅ Passed	All four changed lines are cron schedules; no logging, report-template, credential, token, password, PII, hostname, or customer-data output was added.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@jsafrane: 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.1-periodics-e2e-aws-ovn-conformance-techpreview	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-ovn-conformance-techpreview	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]

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

[jsafrane]

I'm not running pj-rehearse, only frequency was changed. Feel free to run it if you think it's necessary.

[JoelSpeed]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: JoelSpeed, jsafrane
Once this PR has been reviewed and has the lgtm label, please assign csrwng 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

[jsafrane]

/pj-rehearse ack

[openshift-merge-bot]

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