Bug 1821286

Summary:	cluster etcd operator status reporting needs to be more human readable
Product:	OpenShift Container Platform	Reporter:	Alay Patel <alpatel>
Component:	Etcd	Assignee:	Alay Patel <alpatel>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4	CC:	skolicha
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The logs and events about health status are not very readable. Reason: Improper log message construction. Result: Confusing English sentences. Consequence: The events and logs generated could confuse the end user about the status of the cluster. Fix: Properly analyze the statuses in a separate function to construct a proper log message and event about the etcd status. Result: More meaningful reporting of the status of the etcd pods on all master nodes.	Story Points:	---
Clone Of:
Clones:	1823608 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:25:34 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:
Bug Depends On:
Bug Blocks:	1823608

Description Alay Patel 2020-04-06 13:49:11 UTC

Description of problem:
For debugging the cluster-etcd-opertor report how many members are available, unhealthy, unknown or unstarted. If anyone of the lists is empty, it will produce the following output:

-----
EtcdMembers_UnhealthyMembers: EtcdMembersDegraded: ci-op-sd598-m-2.c.openshift-gce-devel-ci.internal members are unhealthy,  members are unknown


Expected output is:

EtcdMembers_UnhealthyMembers: EtcdMembersDegraded: 1 of 3 etcd members (ci-op-sd598-m-2.c.openshift-gce-devel-ci.internal[, ...]) are not reachable.

More discussion from #forum-etcd:

https://coreos.slack.com/archives/C027U68LP/p1585766067158800

Comment 4 ge liu 2020-04-15 10:59:55 UTC

@Alay, do u have any idea for comments3? thanks

Comment 10 errata-xmlrpc 2020-07-13 17:25:34 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:2409