-
Notifications
You must be signed in to change notification settings - Fork 158
CORENET-5389,OCPBUGS-51040,OCPBUGS-54577: [DownstreamMerge] 2025-04-16 #2516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CORENET-5389,OCPBUGS-51040,OCPBUGS-54577: [DownstreamMerge] 2025-04-16 #2516
Conversation
Signed-off-by: Martin Kennelly <[email protected]>
The option "ovn-openflow-probe-interval" is ignored from ovn24.03. Replace it with "ovn-bridge-remote-probe-interval" which serves similar purpose with the difference that from 24.09 it affects all connections to br-int, not only the main thread. At the same time change the default to 0 which is disabled, the inactivity probe shouldn't be needed for connections over unix socket. Signed-off-by: Ales Musil <[email protected]>
Extend the ClusterUserDefinedNetwork (CUDN) spec to enable creating Localnet topology networks. Adjusting the NetworkTopology enum validation and enum validation on the topology Role to fit UDN and CUDN CRDs will be done in follow-up commit. Signed-off-by: Or Mergi <[email protected]>
Localnet topology should be available for CUDN only. Move the NetworkTopology enum validation from shard.go to each definition that use NetworkTopology, having: - UserDefineNetwork CRD spec.topology accepts: Layer2 and Layer3. - ClusterUserDefineNetwork CRD spec.network.topology accepts: Layer2, Layer3 and Localnet. Signed-off-by: Or Mergi <[email protected]>
Localnet topology role should secondary only. Move the NetworkRole enum validation from shard.go to each definition that use NetworkRole, having: - Layer2Config & Layer3Config role field accepts: Secondary and Primary. - LocalnetConfig role field accepts: Secondary only. Signed-off-by: Or Mergi <[email protected]>
Signed-off-by: Or Mergi <[email protected]>
node, metrics: Replace depracated option with equivalent
htmlmin is no longer working with newer versions of python Signed-off-by: Jamo Luhrsen <[email protected]>
Ovnkube-identity pods should run on all control-plane nodes and require that a newly created pod is fully functional before the old one can be terminated and hence require additional pods during upgrades Signed-off-by: nithyar <[email protected]>
Signed-off-by: Enrique Llorente <[email protected]>
Signed-off-by: Enrique Llorente <[email protected]>
Signed-off-by: Enrique Llorente <[email protected]>
Signed-off-by: Enrique Llorente <[email protected]>
We cannot bump to fedora40 until kubevirt v1.5.0 is not used, this is related to [1] [1] kubevirt/kubevirt#13458 Signed-off-by: Enrique Llorente <[email protected]>
Convert to DaemonSet and fix update strategy of ovnkube-identity pods
Signed-off-by: thisisobate <[email protected]>
Signed-off-by: Jamo Luhrsen <[email protected]>
kubevirt, l2, udpn: send unsolicited router advertisement after live migration to reconcile ipv6 default gw
chore: update footer with trademark disclaimer
symlink docs/governance/* to identical files in /
IPv6 Router Advertisements from non-local sources can interfere with primary UDN interfaces in multi-gateway setups, resulting in multiple default gateways. To resolve this, ingress filtering was added using nftables to block unwanted RAs, allowing only RAs from the node's local gateway and RAs with Lifetime 0, which are needed to invalidate entries during migration. Signed-off-by: Or Shoval <[email protected]>
At VM startup the default gw should have only one path after the nftables change at the network namespace Signed-off-by: Enrique Llorente <[email protected]>
BGP routes will be imported to the UDN VRF and GR, when EgressIP for the UDN is advertised to the default VRF. This ensures that the egress traffic can find the right egress route. Signed-off-by: Peng Liu <[email protected]>
UDN: Filter RA according local GW Router LLA only to avoid multi path
@maiqueb: This pull request references Jira Issue OCPBUGS-51040, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
/payload-aggregate periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade 10 |
@tssurya: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9eb88130-1f72-11f0-98ff-7c88c9a425f8-0 |
/payload 4.19 nightly blocking |
@tssurya: trigger 11 job(s) of type blocking for the nightly release of OCP 4.19
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c96f9030-1f72-11f0-9a54-6d9a6e20de5c-0 |
/test e2e-aws-ovn-virt |
Retest following changes has been done on CI to address the issues with AWS lanes openshift/release#64121 /retest-required |
/test e2e-aws-ovn-virt |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kyrtapz, maiqueb, tssurya The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/tide refresh |
windows is failing with:
https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_ovn-kubernetes/2516/pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-windows/1914747326312747008 |
/override ci/prow/e2e-aws-ovn-windows https://issues.redhat.com/browse/WINC-1384 tracks the cert bug for windows |
@tssurya: Overrode contexts on behalf of tssurya: ci/prow/e2e-aws-ovn-windows In response to this:
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. |
/tide refresh |
ced1ea7
into
openshift:master
@maiqueb: Jira Issue OCPBUGS-51040: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-51040 has been moved to the MODIFIED state. Jira Issue OCPBUGS-54577: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-54577 has been moved to the MODIFIED state. In response to this:
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. |
@maiqueb: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
[ART PR BUILD NOTIFIER] Distgit: ovn-kubernetes-base |
[ART PR BUILD NOTIFIER] Distgit: ovn-kubernetes-microshift |
[ART PR BUILD NOTIFIER] Distgit: ose-ovn-kubernetes |
Fix included in accepted release 4.19.0-0.nightly-2025-04-24-005837 |
π Description
This D/S sync brings along primary UDN for virtualization fixes for IPv6.
Fixes #
Additional Information for reviewers
Clean merge, no conflicts.
β Checks
How to verify it