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

Bug 1999704

Summary:	ovn-org/libovsdb should connect to the raft leader when appropriate
Product:	OpenShift Container Platform	Reporter:	Casey Callendrello <cdc>
Component:	Networking	Assignee:	Tim Rozet <trozet>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	medium	CC:	dcbw
Version:	4.9
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2005985 (view as bug list)		Environment:
Last Closed:	2021-09-29 15:33:58 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:
Bug Depends On:
Bug Blocks:	2005985

Description Casey Callendrello 2021-08-31 15:34:28 UTC

When connecting to a clustered ovsdb, ovn-nbctl always connects to the leader. However, ebay/go-ovn doesn't do this.

We should duplicate that behavior.

In order to do it, you need to check the special _Server database that includes information as to whether or not the node is a leader.

You can see a similar implementation for ovn-org/libovsdb in https://github.com/ovn-org/libovsdb/pull/221

Comment 1 Dan Williams 2021-09-20 15:39:35 UTC

Fixed upstream in ovnkube in https://github.com/ovn-org/ovn-kubernetes/pull/2464

Will be pulled into 4.10 when Tim does the next merge to downstream.

Comment 2 Tim Rozet 2021-09-29 15:33:58 UTC


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