Bug 1952176

Summary:	Neutron should not give up trying to connect to OVN DBs
Product:	Red Hat OpenStack	Reporter:	Terry Wilson <twilson>
Component:	python-networking-ovn	Assignee:	Terry Wilson <twilson>
Status:	CLOSED DUPLICATE	QA Contact:	Eran Kuris <ekuris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.1 (Train)	CC:	apevec, ffernand, lhh, majopela, scohen
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-30 17:39:32 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 Terry Wilson 2021-04-21 17:06:00 UTC

Description of problem:
If the OVN.ovsdb_connection_timeout is reached, ovsdbapp's wait_for_change() will raise an Exception. There is no option to not have a timeout. While there may be cases that behavior would be called for for non-Neutron uses, it is a problem for neutron when ovsdb-server is slow and Neutron just fails to start.

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

How reproducible:
100%

Steps to Reproduce:
1. Set OVN.ovsdb_connection_timeout=0 and restart neutron_api

Actual results:
Neutron exits

Expected results:
Neutron continues trying to connect (but with timeout=0, txns will fail)

Comment 2 ffernand 2021-04-30 17:39:32 UTC


*** This bug has been marked as a duplicate of bug 1955271 ***