Bug 1813367

Summary:	add cluster-etcd operator events for membership changes
Product:	OpenShift Container Platform	Reporter:	Suresh Kolichala <skolicha>
Component:	Etcd Operator	Assignee:	Sam Batschelet <sbatsche>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	geliu, sbatsche
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:	1813364	Environment:
Last Closed:	2020-05-04 11:46:21 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:	1813364
Bug Blocks:

Description Suresh Kolichala 2020-03-13 15:31:25 UTC

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

Description of problem:
Adding more events to the log will help figure out problems with membership (unstarted members).

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


How reproducible:


Steps to Reproduce:
1. Install a new cluster (or upgrade from previous version)
2. 
3.

Actual results:
The cluster-etcd-operator log doesn't show issues with membership. For example on IPv6 we were still using DNS name, but the logs didn't show. 

Expected results:
If the logs showed the events about adding member as below, we would have known the problem immediately:
#### attempt 0
      member={name="etcd-bootstrap", peerURLs=[https://[fd2e:6f44:5dd8:c956::18]:2380}, clientURLs=[https://[fd2e:6f44:5dd8:c956::18]:2379]
      member={name="", peerURLs=[https://etcd-0.ostest.test.metalkube.org:2380}, clientURLs=[]
      target={name="", peerURLs=[https://etcd-0.ostest.test.metalkube.org:2380}, clientURLs=[], err=<nil>
Adding the unstarted member to the end master-0.ostest.test.metalkube.org

Additional info:

Comment 5 errata-xmlrpc 2020-05-04 11:46:21 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