NO-JIRA: Parallel syncs for for ovnk branches

[arkadeepsen]

The periodic jobs for syncing the branches 4.21 and 4.18 will now use 5.0 and 4.20 respectively as the source branches. This ensures that parallel sync PRs are opened for 4.22/4.21 and 4.19/4.18 whenever a PR merges in 5.0 and 4.20 respectively.

Summary by CodeRabbit

• Updated OVN-Kubernetes branch-sync jobs in OpenShift CI.
• Branch release-4.21 now syncs from release-5.0.
• Branch release-4.18 now syncs from release-4.20.
• These updates enable parallel sync PRs for the related release branches.

[openshift-ci-robot]

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

Details

In response to this:

The periodic jobs for syncing the branches 4.21 and 4.18 will now use 5.0 and 4.20 respectively as the source branches. This ensures that parallel sync PRs are opened for 4.22/4.21 and 4.19/4.18 whenever a PR merges in 5.0 and 4.20 respectively.

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]

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: Pro Plus

Run ID: 4afcd000-b75b-40c7-8bd6-5ebbba883634

📥 Commits

Reviewing files that changed from the base of the PR and between 4f42d77 and 322ab19.

📒 Files selected for processing (2)

• ci-operator/config/openshift/ovn-kubernetes/openshift-ovn-kubernetes-release-4.18__periodics.yaml
• ci-operator/config/openshift/ovn-kubernetes/openshift-ovn-kubernetes-release-4.21__periodics.yaml

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

Walkthrough

The PR updates two OVN-Kubernetes periodic branch-sync configurations. The release-4.18 job now uses release-4.20 as its source. The release-4.21 job now uses release-5.0 as its source.

Changes

Branch synchronization updates

Layer / File(s)	Summary
Update branch-sync source branches ci-operator/config/openshift/ovn-kubernetes/*periodics.yaml	The release-4.18 sync source changes to release-4.20. The release-4.21 sync source changes to release-5.0. Target branches remain unchanged.

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

Merge Risk: 🔵 Low · up to 322ab

The PR changes the source branches used by two periodic sync jobs. It is mergeable with owner awareness that generated CI metadata and Prow job definitions must be regenerated and verified before merge.

🚥 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 identifies the main change: enabling parallel syncs for OVN-Kubernetes branches.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
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 commit changes only two static SOURCE_BRANCH values in YAML; it adds no Ginkgo It/Describe/Context/When titles or dynamic test-name data.
Test Structure And Quality	✅ Passed	The PR changes only two YAML branch-sync values; it adds no Ginkgo tests or cluster operations subject to this check.
Microshift Test Compatibility	✅ Passed	The pull request changes only two YAML branch-sync SOURCE_BRANCH values; it adds no Ginkgo e2e tests or references to MicroShift-incompatible APIs or features.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR changes only two YAML branch-sync SOURCE_BRANCH values; it adds no Ginkgo e2e tests or test behavior covered by the SNO check.
Topology-Aware Scheduling Compatibility	✅ Passed	The diff only changes SOURCE_BRANCH values in two periodic CI YAML files; it adds no deployment manifests, operator code, controllers, or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The commit changes only two YAML SOURCE_BRANCH values. It adds no OTE binary code or process-level stdout writes; branch-sync references a shell command step.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The commit changes only two YAML SOURCE_BRANCH values for existing branch-sync jobs; it adds no Ginkgo e2e tests or IPv4/external-connectivity behavior.
No-Weak-Crypto	✅ Passed	The HEAD diff only changes SOURCE_BRANCH values in two YAML jobs; no weak-crypto primitive, custom crypto, or secret/token comparison was introduced.
Container-Privileges	✅ Passed	The PR diff changes only SOURCE_BRANCH values in two periodic configs; it adds no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR changes only SOURCE_BRANCH values from release-4.19/4.22 to release-4.20/5.0; no logging code or sensitive values were introduced.

✨ 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.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@arkadeepsen: 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-ovn-kubernetes-release-4.21-periodics-branch-sync	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-ovn-kubernetes-release-4.18-periodics-branch-sync	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.

[arkadeepsen]

/pj-rehearse

[openshift-merge-bot]

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

[openshift-ci]

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

[jluhrsen]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arkadeepsen, jluhrsen

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/ovn-kubernetes/OWNERS [jluhrsen]

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