Reviewed: https://review.opendev.org/c/openstack/neutron/+/988235 Committed: https://opendev.org/openstack/neutron/commit/7a70217d78bd7f90b8c9de4d9341715842d2ee12 Submitter: "Zuul (22348)" Branch: master
commit 7a70217d78bd7f90b8c9de4d9341715842d2ee12 Author: Felix Moebius <[email protected]> Date: Thu May 7 11:59:35 2026 +0200 [OVN] Fix race condition during floating ip deletion The delete path for floating ips currently only deletes the nat entry on the ovn side if it actually finds a nat entry for the floating ip. When quickly associating and then disassociating a floating ip through different neutron api instances, the nat entry may not yet have propagated from one api instance to the other through the northbound if load on the ovsdb is sufficiently high. Since the ovn revision entry is deleted anyways, the maintenance task has no chance of fixing it later on, leaving an orphaned nat entry in ovn which causes connectivity issues when the ip address gets reused. Keep the ovn revision entry in case we don't find a matching nat entry to give the maintenance task a chance to retry the deletion. Related-Bug: #1987530 Signed-off-by: Felix Moebius <[email protected]> Change-Id: I6c598cbbca1e449cf67314d022f101f2f73cf1bc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1987530 Title: Duplicate external_ip in NAT table lead to loss of N/S connectivity To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1987530/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
