Adding the OpenStack Neutron project to this bug after a discussion with the OVN team [4], which suggest that although the current OVN DB schema allows duplicates to occur it is the CMS's responsibility to avoid them.
There is an related neutron bug 1960006 that did attempt to address a similar situation with stale ports in the OVN DB. However it does not appear to be sufficient to avoid this situation. I wonder if Neutron should do a pre-flight check along the lines of what the ``ovn-nbctl`` tool does [5]. 4: https://mail.openvswitch.org/pipermail/ovs-discuss/2022-February/051738.html 5: https://github.com/ovn-org/ovn/blob/ed81be75e8b3b33745eeb9b6ce2686b87ef72cd0/utilities/ovn-nbctl.c#L1392-L1433 ** Also affects: charm-ovn-central Importance: Undecided Status: New ** No longer affects: charm-ovn-central ** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961046 Title: Duplicate IP address on LSPs in the same LS lead to unpredictable flow output To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1961046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
