Description of problem: i have replica 3 listening on ipv6 and i can't mount it from a client over ipv6: [2017-10-30 15:12:03.241527] I [MSGID: 100030] [glusterfsd.c:2496:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.12.1 (args: /usr/sbin/glusterfs --log-level=TRACE --volfile-server=brq-gluster03.example.com --volfile-id=/testdom /mnt) ... [2017-10-30 15:12:03.266359] T [MSGID: 0] [common-utils.c:307:gf_resolve_ip6] 0-resolver: DNS cache not present, freshly probing hostname: brq-gluster03.example.com [2017-10-30 15:12:03.461995] E [MSGID: 101075] [common-utils.c:320:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known) [2017-10-30 15:12:03.462086] E [name.c:267:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host brq-gluster03.example.com [2017-10-30 15:12:03.466859] I [glusterfsd-mgmt.c:2208:mgmt_rpc_notify] 0-glusterfsd-mgmt: disconnected from remote-host: brq-gluster03.example.com # dig +short brq-gluster03.example.com. AAAA 2620:52:0:2588:21a:4aff:fed0:404e # telnet -6 brq-gluster03.example.com 24007 Trying 2620:52:0:2588:21a:4aff:fed0:404e... Connected to brq-gluster03.example.com. Escape character is '^]'. ^] telnet> quit Connection closed. Version-Release number of selected component (if applicable): glusterfs-3.12.1-2.el7.x86_64 / centos-release-7-4.1708.el7.centos.x86_64 How reproducible: 100% Steps to Reproduce: 1. have replica 3 listening on ipv6 2. have a gluster client on ipv6 3. mount -t gluster glusterserver1:/volume /mnt Actual results: i can't mount gluster volume over ipv6 Expected results: should work Additional info:
Created attachment 1345525 [details] mnt.log from client
i did not have time to see if dns query is really done for A or AAAA record, but checking a dns server logs or tcpdumping traffic should reveal it.
Release 3.12 has been EOLd and this bug was still found to be in the NEW state, hence moving the version to mainline, to triage the same and take appropriate actions.
Status?
With glusterfs-6.x and latest glusterfs branches we don't seem to have any IPv6 known issues. Considering this was opened with glusterfs3-12, would like to upgrade and see if this is fixed. Marking it as WORKSFORME with higher versions.