← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1999813] Re: [ovn-octavia-provider] when a HM is created/deleted the listener remains in PENDING_UPDATE

 

Reviewed:  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/867974
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/421665e2d269c47dd9cf9c55183735e3ac110dfc
Submitter: "Zuul (22348)"
Branch:    master

commit 421665e2d269c47dd9cf9c55183735e3ac110dfc
Author: Fernando Royo <froyo@xxxxxxxxxx>
Date:   Fri Dec 16 15:16:03 2022 +0100

    Fix listener provisioning_status after HM created/deleted
    
    When a HM is created/deleted over a pool, the listener related to the
    pool keeps in PENDING_UPDATE status.
    
    This patch return the correct status to Octavia API for the
    listeners related to the pool, ensuring they could be modified and
    not considered as inmutable.
    
    Closes-Bug: #1999813
    Change-Id: I4f6e4a8acb7c7bb030aaadc6875894d6fc00d740


** 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/1999813

Title:
  [ovn-octavia-provider] when a HM is created/deleted  the listener
  remains in PENDING_UPDATE

Status in neutron:
  Fix Released

Bug description:
  When a HM is created/deleted over a pool of a fully populated LB, is
  put the provisioning status of the listener owner of the pool in
  PENDING_UPDATE, the operation is done correctly but the status of the
  listener keeps on that stuck status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1999813/+subscriptions



References