dynamic-routing-port-name option has no effect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ovn (Ubuntu) |
Fix Committed
|
Undecided
|
Unassigned | ||
Plucky |
New
|
Undecided
|
Unassigned | ||
Questing |
New
|
Undecided
|
Unassigned |
Bug Description
[ Impact ]
When using the native OVN dynamic routing feature for learning routes, mapping from which interface a route is learned to a specific LRP is required. Failing to do this will create invalid routes in the system.
The dynamic-
Consequently using dynamic routing to learn routes does not work without this patch.
[ Test Plan ]
The main branch of MicroOVN makes use of this feature [2], and has thorough test suites validating operation. As a form of verification we will build a version of MicroOVN with the -proposed package and provide test results.
[ Where problems could occur ]
OVN 25.03 was the first version with native support for dynamic routing through the use of routing protocol suites such as BIRD or FRR.
As detailed above the route learning feautre is currently not usable, and the fix has been merged to main and backported to 25.09 and 25.03 branches.
Due to the feature currently being broken, the regression potential is minimal or non-existent.
[ Other Info ]
The dynamic-
The description of the option states: "Only learn routes associated with the interface locally bound to the LSP or LRP specified here".
However, when an LR has LRPs with this option, learned routes are still associated with all LRPs of an LR [1].
In order for the option to work as documented there would have to be a check for whether any LRPs of an LR has this option, and if that is the case, only consider those LRPs.
0: https:/
1: https:/
2: https:/
description: | updated |
https:/ /mail.openvswit ch.org/ pipermail/ ovs-dev/ 2025-September/ 426338. html /mail.openvswit ch.org/ pipermail/ ovs-dev/ 2025-September/ 426337. html
https:/