Bug 1940724

Summary:	Stale Logical Router Port entry in OVN blocking any new Octavia LB VIP creation
Product:	Red Hat OpenStack	Reporter:	PURANDHAR SAIRAM MANNIDI <pmannidi>
Component:	python-networking-ovn	Assignee:	Lucas Alvares Gomes <lmartins>
Status:	CLOSED ERRATA	QA Contact:	Eran Kuris <ekuris>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.1 (Train)	CC:	apevec, eolivare, itbrown, jlibosva, lhh, majopela, mdemaced, scohen, sputhenp, vkommadi
Target Milestone:	z6	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-networking-ovn-7.3.1-1.20210412083443.4e24f4c.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-12-09 20:18:11 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 PURANDHAR SAIRAM MANNIDI 2021-03-19 01:43:01 UTC

Description of problem:
In RHOSP 16.1.3 with Octavia-OVN+DVR, OCP deployments with Kuryr SDN might fail because of stale logical router port entries in OVN on subsequest CREATE/DESTROY OCP cluster operations.

Version-Release number of selected component (if applicable):
RHOSP 16.1.3
Neutron ML2/OVN

How reproducible:
Randomly

Steps to Reproduce:
1. Create and destroy OCP with Kuryr deployments on OSP.


Actual results:
Neutron doesn't cleanup all the logical router ports in OVN before deleting in Neutron DB.

Expected results:
Neutron should cleanup all the logical router ports in OVN before deleting in Neutron DB

Additional info:

Comment 3 Eva Huang 2021-03-22 02:11:54 UTC

This is proactive escalation case, it's highlighted the customer has issue when OCP 4.x Deployment on OSP 16.x and would like your attention to look into it and help providing observation and update. Escalation flag is set. Thank you.

Comment 4 Eduardo Olivares 2021-03-23 14:37:38 UTC

*** Bug 1940870 has been marked as a duplicate of this bug. ***

Comment 5 Lucas Alvares Gomes 2021-03-23 16:37:39 UTC

Hi,

I've added a fix upstream for this issue at: https://review.opendev.org/c/openstack/neutron/+/782551. Once merged, I will work on backporting it to the stable branches.

As a workaround for this problem, the stale Logical_Router_Port entry could be manually deleted from the OVN NB database with the following command:

$ ovn-nbctl lrp-del lrp-<Neutron router port UUID>

Cheers,
Lucas

Comment 18 Itzik Brown 2021-08-02 14:09:43 UTC

Checked with Openshift on Openstack 
RHOS-16.1-RHEL-8-20210727.n.1
4.8.0-0.nightly-2021-07-29-020730

After each Openshift deletion I ran neutron-ovn-db-sync-util --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --ovn-neutron_sync_mode log and checked that the command didn't resulted with errors and reinstalled Openshift again

Comment 32 errata-xmlrpc 2021-12-09 20:18:11 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.7 (Train) 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:3762