Bug 1808546

Summary:	The discover-etcd-initial-cluster tool should return no error if member dir exists, and cannot get client or target member
Product:	OpenShift Container Platform	Reporter:	Suresh Kolichala <skolicha>
Component:	Etcd	Assignee:	Suresh Kolichala <skolicha>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	geliu
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:	1808544	Environment:
Last Closed:	2020-05-04 11:43:49 UTC	Type:	---
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:	1808544
Bug Blocks:

Description Suresh Kolichala 2020-02-28 19:15:34 UTC

+++ This bug was initially created as a clone of Bug #1808544 +++

Description of problem:
In lights-out scenario (turn the lights off and on again scenario), the calls get client will return error. However, because discover-etcd-initial-cluster return error currently, etcd never gets to start.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Turn all the master nodes off on a running cluster.
2. Turn them back on.


Actual results:
etcd fails to come up. crictl logs show that discover-etcd-initial-cluster is returning error.

Expected results:
etcd, API server and rest of the cluster should be up.

Additional info:

Comment 5 errata-xmlrpc 2020-05-04 11:43:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581