Bug 2222828

Summary:	[Known Issue] Replacing controller node leads to OVN database partition
Product:	Red Hat OpenStack	Reporter:	ldenny
Component:	documentation	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	NEW ---	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	17.0 (Wallaby)	CC:	jamsmith, ykarel
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:		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 ldenny 2023-07-13 23:57:26 UTC

Description of problem:
This bug is in relation to https://bugzilla.redhat.com/show_bug.cgi?id=2222543

Where we have identified when replacing a controller node we don't have logic to handle cleaning up the stale node from OVN and we don't have logic for the new controller node to join the cluster causing a OVN database partition if the controller is the bootstrap node.

Until this bug is fixed, we need a warning added to the documentation for controller replacement.


Version-Release number of selected component (if applicable):
RHOSP17.0
RHOSP17.1


How reproducible:
Every time


All extra details are provided in https://bugzilla.redhat.com/show_bug.cgi?id=2222543

Comment 3 Greg Rakauskas 2023-08-07 19:05:45 UTC

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