Bug 1808544 - The discover-etcd-initial-cluster tool should return no error if member dir exists, and cannot get client or target member
Summary: The discover-etcd-initial-cluster tool should return no error if member dir e...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.5.0
Assignee: Suresh Kolichala
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks: 1808546
TreeView+ depends on / blocked
 
Reported: 2020-02-28 19:07 UTC by Suresh Kolichala
Modified: 2020-08-04 18:02 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1808546 (view as bug list)
Environment:
Last Closed: 2020-08-04 18:02:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-08-04 18:02:34 UTC

Description Suresh Kolichala 2020-02-28 19:07:43 UTC
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-08-04 18:02:32 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 (OpenShift Container Platform 4.5 image release 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:2409


Note You need to log in before you can comment on or make changes to this bug.