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

Bug 1804906

Summary:	etcd does not recover from all masters down
Product:	OpenShift Container Platform	Reporter:	David Eads <deads>
Component:	Etcd Operator	Assignee:	Sam Batschelet <sbatsche>
Status:	CLOSED DUPLICATE	QA Contact:	ge liu <geliu>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4	CC:	skolicha, vareti
Target Milestone:	---
Target Release:	4.4.0
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-03-10 16:42:49 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 David Eads 2020-02-19 20:51:09 UTC

The current etcd static pod is very predictable, but it relies on having a cluster to contact before starting the cluster.

It needs to be able to recover from an "all masters stopped and started" scenario.  With node IPs, node names, and node DNS remaining the same.

One possible way to do this is to have a static pod make a mark in the known location on disk that indicates that it has successfully joined before and the string it used to join.  In this way, it could re-use this string for later restarts.  I would suggest keeping this string on a per-revision basis.