Reviewed: https://review.opendev.org/c/openstack/neutron/+/853840 Committed: https://opendev.org/openstack/neutron/commit/d237a2a83034fab809517a39dddee15995226131 Submitter: "Zuul (22348)" Branch: master
commit d237a2a83034fab809517a39dddee15995226131 Author: Jakub Libosvar <[email protected]> Date: Fri Aug 19 20:16:09 2022 +0000 ovn: Don't fail db sync if new IP allocation fails for metadata There is a scenario where IP allocation pool is depleted but OVN metadata port got removed its IP manually. The DB sync script will attempt to allocate a new IP address if DHCP is enabled in the subnet. Since the pool has no available IP addresses an exception is raised and the whole db sync stops. This patch simply catches the exception, logs and error and continues syncing other resources. Closes-bug: #1987135 Signed-off-by: Jakub Libosvar <[email protected]> Change-Id: Iaa7b0d7ceb244a38fddd7676066683bf2ca72341 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1987135 Title: ovn: db sync fails if all ips are allocated in the subnet and metadata port is missing an ip Status in neutron: Fix Released Bug description: If a user creates a tenant network with small subnet (like /30) and then manually deletes IP address from the metadata port and allocates all available IP addresses then db sync will fail when attempting to allocate a new IP address to the metadata port. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1987135/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
