Bug 1955271

Summary:	[ovn] ml2/ovn may time out connecting to ovsdb server and stays dead in the water
Product:	Red Hat OpenStack	Reporter:	ffernand <ffernand>
Component:	python-networking-ovn	Assignee:	ffernand <ffernand>
Status:	CLOSED ERRATA	QA Contact:	Eduardo Olivares <eolivare>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	16.1 (Train)	CC:	apevec, jlibosva, lhh, majopela, scohen, twilson
Target Milestone:	z7	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.20210428163718.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-12-09 20:19:04 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 ffernand 2021-04-29 19:19:05 UTC

Right now, the IDL connections between ml2/ovn are not resilient
enough when connecting. It doesn't make sense to give up on that
since the ml2/ovn is useless w/out that access.

If ovsdb-server is slow and takes more than timeout seconds, everything
reconnecting after partial downloads and starting over is not going to
make things better. That is particularly likely to happen when the OVN
DB is very large.

Comment 3 ffernand 2021-04-30 17:39:29 UTC

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

Comment 25 errata-xmlrpc 2021-12-09 20:19:04 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