PTPCI: add 90m between paired nightly PTP jobs

[nocturnalastro]

Move 4.22 and 5.0-upstream from 06:00 to 07:30 UTC so they start ~7.5h after the preceding install job on the shared ptpcimno cluster, matching observed runtimes that sometimes stretch past six hours including gather.

Generated-by: Cursor

Summary by CodeRabbit

Moves the 4.22 and 5.0-upstream nightly PTP jobs from 06:00 to 07:30 UTC on their scheduled days. This creates a 90-minute gap between paired jobs on the shared ptpcimno cluster and allows about 7.5 hours after the preceding install job.

[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: 59567c4b-09c0-4963-ac90-4cf6001d14a7

📥 Commits

Reviewing files that changed from the base of the PR and between 4059300 and f32b774.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• ci-operator/config/openshift/release/openshift-release-main__nightly-4.22.yaml
• ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml

---

Walkthrough

The PR updates two nightly telco PTP CI job schedules from 06:00 to 07:30 while preserving their existing run days.

Changes

Telco PTP schedule updates

Layer / File(s)	Summary
Update telco PTP cron schedules ci-operator/config/openshift/release/openshift-release-main__nightly-4.22.yaml, ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml	The 4.22 and 5.0 telco PTP jobs now run at 07:30 on their existing schedules.

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

Possibly related PRs

• openshift/release#82614: Updates scheduled CI job cron expressions in OpenShift configuration files.
• openshift/release#82853: Updates cron schedules for periodic OpenShift CI jobs.

Suggested labels: lgtm, approved, ok-to-test, rehearsals-ack

Suggested reviewers: kasturinarra, vr4manta

🚥 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 describes adding a 90-minute gap between paired nightly PTP jobs, which matches the main pull request objective.
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 patch changes only cron schedules in two test configs and the generated periodics file; it adds no Ginkgo test titles or dynamic test-name values.
Test Structure And Quality	✅ Passed	The pull request changes only CI YAML cron schedules; it adds or modifies no Ginkgo test code, so these test-quality requirements do not apply.
Microshift Test Compatibility	✅ Passed	The patch only changes cron schedules in YAML and generated periodic jobs; it adds no Ginkgo tests or API/resource references requiring MicroShift compatibility review.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The commit changes only three CI YAML schedules; it adds no Ginkgo tests or test source, so SNO compatibility checks are not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	The PR changes only CI cron expressions in two test configs and the generated periodics file; it adds no deployment, operator, controller, or topology scheduling constraint.
Ote Binary Stdout Contract	✅ Passed	The PR changes only three YAML cron fields from 06:00 to 07:30; it adds no OTE process-level code or stdout/logging writes.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The commit changes only three YAML cron schedules. It adds no Ginkgo tests, IPv4 assumptions, or external connectivity requirements.
No-Weak-Crypto	✅ Passed	PR contains only scheduling time changes in YAML config files. No cryptographic code, algorithms, or weak crypto usage present. Check not applicable.
Container-Privileges	✅ Passed	The PR changes only four cron values in two test configs and two generated periodic jobs; no privileged, host namespace, SYS_ADMIN, root, or allowPrivilegeEscalation settings were added.
No-Sensitive-Data-In-Logs	✅ Passed	The PR changes only four cron replacements in configuration and generated periodics files; no logging statements or sensitive data appear in added lines.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{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: nocturnalastro
Once this PR has been reviewed and has the lgtm label, please assign dgoodwin 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/release/OWNERS
• ci-operator/jobs/openshift/release/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]
@nocturnalastro: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.
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-release-main-nightly-4.22-e2e-telco5g-ptp
periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-ptp-upstream

[openshift-ci]

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