commit 2b0dc5bd4b4f39cb0783fb77c7e344e11428cbdd
Author: Luis Tomas Bolivar <email address hidden>
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
(cherry picked from commit 28c50d9147fed8e9757ba073929ce5a547e90f03)
Reviewed: https:/ /review. opendev. org/c/openstack /ovn-octavia- provider/ +/835653 /opendev. org/openstack/ ovn-octavia- provider/ commit/ 2b0dc5bd4b4f39c b0783fb77c7e344 e11428cbdd
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/yoga
commit 2b0dc5bd4b4f39c b0783fb77c7e344 e11428cbdd
Author: Luis Tomas Bolivar <email address hidden>
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 4ab061645a7221a 541cd183aa7 9757ba073929ce5 a547e90f03)
Change-Id: I7701ac3ab7358d
(cherry picked from commit 28c50d9147fed8e