+++ 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:
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