Bug 1804913

Summary: etcd still fails on IPv6 cluster
Product: OpenShift Container Platform Reporter: Dan Winship <danw>
Component: Etcd OperatorAssignee: Sam Batschelet <sbatsche>
Status: CLOSED ERRATA QA Contact: ge liu <geliu>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.4CC: bparees, dmace
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1810694 (view as bug list) Environment:
Last Closed: 2020-07-13 17:16:20 UTC Type: Bug
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:    
Bug Blocks: 1810694    
Attachments:
Description Flags
etcd.log
none
/etc/kubernetes from bootstrap node none

Description Dan Winship 2020-02-19 21:23:01 UTC 
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)
Comment 1 Dan Winship 2020-02-19 21:37:15 UTC 
Created attachment 1664209 [details]
/etc/kubernetes from bootstrap node
Comment 4 ge liu 2020-03-02 11:00:25 UTC 
blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1805936
Comment 6 ge liu 2020-05-25 10:00:00 UTC 
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.
Comment 9 errata-xmlrpc 2020-07-13 17:16:20 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:2409