Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/834335 Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/28c50d9147fed8e9757ba073929ce5a547e90f03 Submitter: "Zuul (22348)" Branch: master
commit 28c50d9147fed8e9757ba073929ce5a547e90f03 Author: Luis Tomas Bolivar <[email protected]> Date: Fri Mar 18 17:52:21 2022 +0100 Avoid loadbalancer stuck in PENDING_X if delete_vip_port fails If either on a failed loadbalancer creation action, or in a loadbalancer deletion, the delete_vip_port fails with a different exception than PortNotFound (for instance, if neutron API is unreachable at that time), the loadbalancer will remain stuck in PENDING_X, as the ERROR status is not returned Closes-Bug: #1965732 Change-Id: I7701ac3ab7358d4ab061645a7221a541cd183aa7 ** 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/1965732 Title: [ovn-octavia-provider] loadbalancer stuck in PENDING_X if delete_vip_port fails Status in neutron: Fix Released Bug description: Load balancer are stuck in pending_x status if delete_vip_port function fails with an error different than PortNotFound when:: - deleting a loadbalancer - failed to created a loadbalancer The problem comes from proper status update not being sent back to octavia To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1965732/+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
