Bug 2159684 - Fully populated HM is created/deleted, the listener remains in PENDING_UPDATE
Summary: Fully populated HM is created/deleted, the listener remains in PENDING_UPDATE
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-ovn-octavia-provider
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ga
: 17.1
Assignee: Fernando Royo
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks: 2143732
TreeView+ depends on / blocked
 
Reported: 2023-01-10 11:43 UTC by Fernando Royo
Modified: 2023-09-24 17:27 UTC (History)
0 users

Fixed In Version: python-ovn-octavia-provider-1.0.3-1.20221227155353.0d529f7.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 01:13:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1999813 0 None None None 2023-01-10 11:43:26 UTC
OpenStack gerrit 868386 0 None MERGED Fix listener provisioning_status after HM created/deleted 2023-01-20 10:35:20 UTC
Red Hat Issue Tracker OSP-21287 0 None None None 2023-01-10 11:50:27 UTC
Red Hat Product Errata RHEA-2023:4577 0 None None None 2023-08-16 01:13:31 UTC

Description Fernando Royo 2023-01-10 11:43:27 UTC 
When a HM is created/deleted over a pool of a fully populated LB, it 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.
Comment 8 Lukas Svaty 2023-06-16 08:13:29 UTC 
Bulk moving target milestone to GA after the release of Beta on 14th June '23.
Comment 15 errata-xmlrpc 2023-08-16 01:13:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:4577
Note You need to log in before you can comment on or make changes to this bug.