Neutron-dynamic-routing does not work with OVN

Bug #1959666 reported by Dr. Jens Harbott
This bug affects 8 people
Affects Status Importance Assigned to Milestone
OpenStack Neutron API OVN Plugin Charm
Fix Committed
OpenStack Neutron Dynamic Routing charm
In Progress
Ubuntu Cloud Archive
Fix Released

Bug Description

When using OVN as Neutron backend, announcing prefixes with neutron-dynamic-routing is currently not working due to changes in the database structure. Some attempt to fix this has been made in but wasn't successful.

This is a major stop gap for production deployments which are using BGP to provide connectivity for IPv6 subnets in tenant networks.

Tags: ipv6 l3-bgp ovn
Changed in neutron:
status: New → Confirmed
Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :

I believe this issue was addressed in

However, there are some other considerations around distributed floating IPs with OVN and the extra router attributes in the context of OVN routers relevant to NDR:

Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

Ack, OVN+NDR is working in general now, some specific use case may still need additional work.

Changed in neutron:
status: Confirmed → Fix Released
Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote (last edit ):

When it comes to the NDR charm we enabled it in the charms (neutron-api-plugin-ovn specifically needed a code change) documenting those limitations in the charm-guide.

Also we are adding some data plane testing to make sure that the advertised routes are actually possible to reach.

Changed in charm-neutron-api-plugin-ovn:
status: New → Fix Committed
Changed in charm-neutron-dynamic-routing:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.