Verified with 4.5.0-0.nightly-2020-09-20-185910 sh-4.2# etcdctl endpoint health https://10.0.52.27:2379 is healthy: successfully committed proposal: took = 9.617947ms https://10.0.49.196:2379 is healthy: successfully committed proposal: took = 10.715916ms https://10.0.75.193:2379 is healthy: successfully committed proposal: took = 15.897101ms # oc describe pods etcd-ip-10-0-49-196.us-east-2.compute.internal Environment: ALL_ETCD_ENDPOINTS: https://10.0.49.196:2379,https://10.0.52.27:2379,https://10.0.75.193:2379 ETCDCTL_API: 3 ETCDCTL_CACERT: /etc/kubernetes/static-pod-certs/configmaps/etcd-serving-ca/ca-bundle.crt ETCDCTL_CERT: /etc/kubernetes/static-pod-certs/secrets/etcd-all-peer/etcd-peer-ip-10-0-49-196.us-east-2.compute.internal.crt ETCDCTL_ENDPOINTS: https://10.0.49.196:2379,https://10.0.52.27:2379,https://10.0.75.193:2379 ETCDCTL_KEY: /etc/kubernetes/static-pod-certs/secrets/etcd-all-peer/etcd-peer-ip-10-0-49-196.us-east-2.compute.internal.key
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.13 bug fix update), 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:3760