Bug 2159684

Summary:	Fully populated HM is created/deleted, the listener remains in PENDING_UPDATE
Product:	Red Hat OpenStack	Reporter:	Fernando Royo <froyo>
Component:	python-ovn-octavia-provider	Assignee:	Fernando Royo <froyo>
Status:	CLOSED ERRATA	QA Contact:	Eran Kuris <ekuris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	17.0 (Wallaby)	Keywords:	Triaged
Target Milestone:	ga
Target Release:	17.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-ovn-octavia-provider-1.0.3-1.20221227155353.0d529f7.el8ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-16 01:13:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2143732

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