*** Bug 1811530 has been marked as a duplicate of this bug. ***
*** Bug 1812409 has been marked as a duplicate of this bug. ***
Verified the OCP build 4.4.0-0.nightly-2020-03-15-215151, steps see below,
$ oc get kubeapiserver/cluster -o json | jq .spec.observedConfig.storageConfig
logged into the master node and searching related keywords,
$ oc get nodes
NAME STATUS ROLES AGE VERSION
keosp1641-wq2sw-master-0 Ready master 20h v1.17.1
keosp1641-wq2sw-master-1 Ready master 20h v1.17.1
keosp1641-wq2sw-master-2 Ready master 20h v1.17.1
keosp1641-wq2sw-worker-lzdx2 Ready worker 20h v1.17.1
keosp1641-wq2sw-worker-s4j54 Ready worker 20h v1.17.1
keosp1641-wq2sw-worker-z29ml Ready worker 20h v1.17.1
$ oc debug node/keosp1641-wq2sw-master-0
Starting pod/keosp1641-wq2sw-master-0-debug ...
To use host binaries, run `chroot /host`
Pod IP: 192.168.0.30
If you don't see a command prompt, try pressing enter.
sh-4.2# chroot /host
sh-4.4# cd /var/log/pods
sh-4.4# grep -nr 'https://etcd' openshift*
sh-4.4# grep -nr 'host-etcd' openshift*
openshift-sdn_sdn-bjc8m_5a8057be-25de-476a-9d95-2af82aba2cf1/sdn/0.log:74:2020-03-16T07:23:11.384356349+00:00 stderr F I0316 07:23:11.384325 3480 roundrobin.go:235] LoadBalancerRR: Setting endpoints for openshift-etcd/host-etcd:etcd to [192.0.2.2:2379 192.0.2.200:2379 192.0.2.3:2379 192.0.2.4:2379]
openshift-sdn_sdn-bjc8m_5a8057be-25de-476a-9d95-2af82aba2cf1/sdn/0.log:82:2020-03-16T07:23:11.384673997+00:00 stderr F I0316 07:23:11.384664 3480 roundrobin.go:235] LoadBalancerRR: Setting endpoints for openshift-etcd/host-etcd-2:etcd to [192.168.0.22:2379 192.168.0.24:2379 192.168.0.30:2379]
The above found ‘host-etcd’ in log file, it is reasonable at present stage, see https://bugzilla.redhat.com/show_bug.cgi?id=1810133#c8, move the bug verify.
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.