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

Bug 1927928

Summary:	[Octavia] Deleting LB or L7 policies results into error
Product:	Red Hat OpenStack	Reporter:	Priscila <pveiga>
Component:	openstack-octavia	Assignee:	Gregory Thiemonge <gthiemon>
Status:	CLOSED ERRATA	QA Contact:	Bruna Bonguardo <bbonguar>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.1 (Train)	CC:	alolivei, amaron, cgoncalves, gthiemon, ihrachys, lpeer, majopela, njohnston, scohen
Target Milestone:	z5	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-octavia-5.0.3-1.20201114024053.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-26 13:51:28 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:

Description Priscila 2021-02-11 20:51:01 UTC

Description of problem:  Deleting LB or L7 policies results into error

After upgrading from OSP13 to OSP16.1 customer started to face not only [1] but also [2].

While in OSP13 they didnt really fixed the [1] but did the upgrade "workarounding" the problem like mentioned in the resolution of [3].
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1724652
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1655431#c16
[3] https://access.redhat.com/solutions/4251821


Log summary:

* The amphora xxx with IP xxx is missing from the DB so it cannot be automatically deleted an operator must manually delete it from the compute service.
* octavia-delete-l7policy-flow': netaddr.core.AddrFormatError: failed to detect a valid IP address from None


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. Create an LB
2. Delete it, it will get into error state
3. Apply resolution of [3], it might work

4. Create an L7 policy in a running active LB, It will get into error state
5. Try to delete it wont work, no error msg
6. Try to delete the LB will make we fall into step 2 ;)

Actual results: Cant escalate LBs

Expected results: Be able to delete LBs and create and delete L7 policies.

Additional info: Similar issue
~~~
https://bugzilla.redhat.com/show_bug.cgi?id=1641827
https://bugzilla.redhat.com/show_bug.cgi?id=1577976
https://bugzilla.redhat.com/show_bug.cgi?id=1655431
~~~

Comment 16 Gregory Thiemonge 2021-02-25 16:29:41 UTC

That looks really similar to this upstream story: https://storyboard.openstack.org/#!/story/2008099

The fix for this issue is https://review.opendev.org/c/openstack/octavia/+/756902, it's already included in 16.2

Comment 49 Arieh Maron 2021-04-29 13:17:07 UTC

Verified by Arieh Maron 2021-04-29 
Red Hat OpenStack Platform release 16.1.6 GA (Train)
RHOS-16.1-RHEL-8-20210421.n.1

Comment 51 Arieh Maron 2021-05-04 07:04:33 UTC

I wasn't able to reproduce it which I considered verification that the issue is no longer an issue.

Comment 57 errata-xmlrpc 2021-05-26 13:51:28 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 16.1.6 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-2021:2097