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].
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.openvswit ch.org/ pipermail/ ovs-discuss/ 2022-February/ 051738. html /github. com/ovn- org/ovn/ blob/ed81be75e8 b3b33745eeb9b6c e2686b87ef72cd0 /utilities/ ovn-nbctl. c#L1392- L1433
5: https:/