Bug 1890286

Summary:	ovnkube-master ends in CrashLoopBackOff during master node replacement; ovsdb-server: ovsdb error: error reading record 6439 from OVN_Northbound log: record 6439 indicates server has left the cluster; it cannot be added back
Product:	OpenShift Container Platform	Reporter:	Marius Cornea <mcornea>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	urgent
Priority:	unspecified	CC:	trozet
Version:	4.6	Keywords:	TestBlocker
Target Milestone:	---
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:	2020-10-21 19:52:41 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 Marius Cornea 2020-10-21 19:39:53 UTC

Description of problem:

ovnkube-master ends in CrashLoopBackOff during master node replacement; nbdb reports: ovsdb-server: ovsdb error: error reading record 6439 from OVN_Northbound log: record 6439 indicates server has left the cluster; it cannot be added back (use "ovsdb-tool join-cluster" to add a new server)


Version-Release number of selected component (if applicable):
4.6.0-rc.4

How reproducible:
100%

Steps to Reproduce:
1. Deploy a baremetal IPI setup with OVNKubernetes

2. Run throught the master node replacement procedure according to:

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.5/html-single/backup_and_restore/index#restore-replace-stopped-etcd-member_replacing-unhealthy-etcd-member

Actual results:

When the master node replacement comes up ovnkube-master pod ends up in CrashLoopBackOff

Expected results:
ovnkube-master starts without errors

Additional info:

Comment 2 Tim Rozet 2020-10-21 19:52:41 UTC


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