neutron

  1. Bug #1965732
  2. Comment #14

Comment 14 for bug 1965732

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ovn-octavia-provider (stable/victoria)

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/835656
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/e96ad123808bc2bb121c7e4a997c1426a7ce7e07
Submitter: "Zuul (22348)"
Branch: stable/victoria

commit e96ad123808bc2bb121c7e4a997c1426a7ce7e07
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

    Also modified coverage to 88% just to allow backport on victoria stable
    branch. Following patch [1] includes several tests over the code base
    of this current patch and will restore the threshold again to 90 when
    it is be backported.

    [1] https://review.opendev.org/c/openstack/ovn-octavia-provider/+/836033

    Closes-Bug: #1965732
    Change-Id: I7701ac3ab7358d4ab061645a7221a541cd183aa7
    (cherry picked from commit 28c50d9147fed8e9757ba073929ce5a547e90f03)