Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2131710

Summary: Deleting a LoadBalancer remains in ERROR status
Product: Red Hat OpenStack Reporter: Fernando Royo <froyo>
Component: python-networking-ovnAssignee: Fernando Royo <froyo>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: apevec, ekuris, itbrown, jschluet, lhh, majopela, scohen, stchen
Target Milestone: z4Keywords: Regression, Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-networking-ovn-7.4.2-2.20220409154865.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2131709 Environment:
Last Closed: 2022-12-07 19:25:51 UTC Type: ---
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: 2131709, 2131712    
Bug Blocks:    

Description Fernando Royo 2022-10-03 12:12:06 UTC
+++ This bug was initially created as a clone of Bug #2131709 +++

Sometimes when the env is over a heavy load, the deletion of a loadbalancer finalizes on ERROR status without any reason aparently.

It is difficult to reproduce but after some revision of logs it looks related to the delete operation over all references where the LB is participating. if any of those references is not found the log shows:

Exception.idlRowNotFound

Comment 7 Itzik Brown 2022-11-28 10:27:24 UTC
Verified with 

OSP RHOS-16.2-RHEL-8-20221124.n.1
OCP 4.10.43

Ran 3 times conformance tests and there was no LB in non-active state.

Comment 12 errata-xmlrpc 2022-12-07 19:25:51 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 16.2.4), 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/RHBA-2022:8794