Bug 2131709 - Deleting a LoadBalancer remains in ERROR status
Summary: Deleting a LoadBalancer remains in ERROR status
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: z1
: 17.0
Assignee: Fernando Royo
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks: 2131710 2131712
TreeView+ depends on / blocked
 
Reported: 2022-10-03 12:09 UTC by Fernando Royo
Modified: 2023-01-25 12:30 UTC (History)
0 users

Fixed In Version: python-ovn-octavia-provider-1.0.1-0.20221122190308.bbf881f.el9ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2131710 2131712 (view as bug list)
Environment:
Last Closed: 2023-01-25 12:29:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 857716 0 None MERGED Avoid LB ERROR status on delete when LS/LR are already deleted 2022-10-03 12:10:33 UTC
OpenStack gerrit 859531 0 None MERGED Avoid LB ERROR status on delete when LS/LR are already deleted 2022-10-03 12:10:33 UTC
Red Hat Issue Tracker OSP-19070 0 None None None 2022-10-03 12:22:46 UTC
Red Hat Product Errata RHBA-2023:0271 0 None None None 2023-01-25 12:30:28 UTC

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
Note You need to log in before you can comment on or make changes to this bug.