Description of problem: As reported on IRC by alex88, gluster isn't resolving hosts that have only IPv6 DNS entries (ie AAAA instead of A). [2013-03-18 10:23:42.211253] I [glusterfsd.c:1666:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.3.1 [2013-03-18 10:23:42.213462] E [common-utils.c:125:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known) [2013-03-18 10:23:42.213537] E [name.c:243:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host storage.site.com [2013-03-18 10:23:42.213609] E [glusterfsd-mgmt.c:1787:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: Success [2013-03-18 10:23:42.213649] I [glusterfsd-mgmt.c:1790:mgmt_rpc_notify] 0-glusterfsd-mgmt: -1 connect attempts left [2013-03-18 10:23:42.213846] W [glusterfsd.c:831:cleanup_and_exit] (-->/usr/sbin/glusterfs(glusterfs_mgmt_init+0x1ff) [0x7f38a41a41af] (-->/usr/lib/libgfrpc.so.0(rpc_clnt_start+0x12) [0x7f38a3af0922] (-->/usr/sbin/glusterfs(+0xd486) [0x7f38a41a4486]))) 0-: received signum (1), shutting down [2013-03-18 10:23:42.213905] I [fuse-bridge.c:4648:fini] 0-fuse: Unmounting '/mnt/site-development/'. Version-Release number of selected component (if applicable): glusterfs 3.3.1 built on Feb 21 2013 03:24:40 "got by the ubuntu ppa" How reproducible: Every time. Steps to Reproduce: 1. Install gluster. 2. Attempt to use a host that only has AAAA DNS records. 3. Fails here.
We need IPv6 for 3.6. Can we make this a priority for this cycle?
It'll probably depend on the code for "Better Peer Identification" getting in first: http://www.gluster.org/community/documentation/index.php/Features/Better_peer_identification If that gets in with sufficient lead time, it might be possible to add IPv6 support for 3.6 as well. Probably need to ask Kaushal if he thinks its feasible.
This is still a problem with 3.5.0, it looks like almost all ipv6 support got ripped out with commit 3dc56cbd16b1074d7ca1a4fe4c5bf44400eb63ff :-(
I see similar problems in a dual-stack setup.
Reverting 3dc56cbd16b1074d7ca1a4fe4c5bf44400eb63ff (with one small manual merge) made IPv6 work for me. :-) Let's hope it gets into 3.6.
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug. If there has been no update before 9 December 2014, this bug will get automatocally closed.
Problem still exists in 3.5.
Will this be fixed in the 3.5 branch? Any plan for the release of 3.5.x?
because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.