Bug 1952176 - Neutron should not give up trying to connect to OVN DBs
Summary: Neutron should not give up trying to connect to OVN DBs
Keywords:
Status: CLOSED DUPLICATE of bug 1955271
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Terry Wilson
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-21 17:06 UTC by Terry Wilson
Modified: 2022-08-23 18:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-30 17:39:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 787310 0 None NEW Don't ever give up trying to connect to OVN DBs 2021-04-21 17:06:00 UTC
Red Hat Issue Tracker OSP-3227 0 None None None 2022-08-23 18:35:17 UTC

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