-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
2
-
False
-
-
False
-
ovn26.03-26.03.0-beta.8.el10fdp
-
rhel-10
-
None
-
rhel-net-ovn
-
-
-
ssg_networking
What's the feature?
The EVPN feature is still marked as experimental so until we make it fully supported we can still change user facing configuration.
As discussed in https://issues.redhat.com/browse/FDP-3104?focusedId=29001706&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-29001706 the CMS will most likely never use default values. And the defaults don't allow dual-stack.
So it's probably better to remove the defaults all together and log a warning if the CMS doesn't configure them.
NOTE: this was discussed as an exception for inclusion to 26.03 upstream here: https://mail.openvswitch.org/pipermail/ovs-dev/2026-February/430133.html
Why is it needed?
It's a required change before we mark the feature as non-experimental as it reduces the amount of stuff we need to support.
Who will benefit?
OVN devs and maintainers.
- clones
-
FDP-3136 Upstream: [EVPN] Remove dynamic-routing-bridge/vxlan/advertise-ifname defaults.
-
- Closed
-