Bug 2131709

Summary: Deleting a LoadBalancer remains in ERROR status
Product: Red Hat OpenStack Reporter: Fernando Royo <froyo>
Component: python-ovn-octavia-providerAssignee: 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: z1   
Target Release: 17.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-ovn-octavia-provider-1.0.1-0.20221122190308.bbf881f.el9ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2131710 2131712 (view as bug list) Environment:
Last Closed: 2023-01-25 12:29:56 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: 2131710, 2131712    

Description Fernando Royo 2022-10-03 12:09:13 UTC
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 12 errata-xmlrpc 2023-01-25 12:29:56 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 (Red Hat OpenStack Platform 17.0.1 bug fix and enhancement advisory), 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-2023:0271