Created attachment 1664207 [details] etcd.log With cluster-etcd-operator master, etcd start initially fails due to unescaped IPv6 IPs in URLs. https://github.com/openshift-kni/cluster-etcd-operator/commit/ac70e6b3 is one fix for this. (Maybe it would make more sense to fix the environment variable where it's defined but I couldn't figure out where it was defined.) With that fix it still fails because: 2020-02-19 20:29:59.567186 I | embed: rejected connection from "[fc00::7]:45824" (error "tls: \"fc00::7\" does not match any of DNSNames [\"dwinship-ipv6.sdn.azure.devcluster.openshift.com\"] (lookup dwinship-ipv6.sdn.azure.devcluster.openshift.com on 168.63.129.16:53: no such host)", ServerName "etcd-0.dwinship-ipv6.sdn.azure.devcluster.openshift.com", IPAddresses ["10.0.0.8"], DNSNames ["dwinship-ipv6.sdn.azure.devcluster.openshift.com"]) 2020-02-19 20:29:59.616916 W | etcdserver: could not get cluster response from https://10.0.0.8:2380: Get https://10.0.0.8:2380/members: EOF 2020-02-19 20:29:59.620906 C | etcdmain: cannot fetch cluster info from peer urls: could not retrieve cluster information from the given urls ("10.0.0.8" and "fc00::7" are both the bootstrap node)
Created attachment 1664209 [details] /etc/kubernetes from bootstrap node
blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1805936
The 4.5 ipv6 cluster still unavailable in QE, and we tried it on 4.4 ipv6 cluster before, it works well, so we will try to verify it after 4.5 ipv6 cluster ready.
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