Description of problem: Gluster struggles in pure IPv6 environment. Setting transport.address-family is not a complete solution at runtime and compile-time defaults to IPv4. At least a compile time IPv6 default option is needed.
REVIEW: http://review.gluster.org/16228 (gluster: IPv6 single stack support) posted (#1) for review on master by Kevin Vigor (kvigor)
REVIEW: http://review.gluster.org/16228 (gluster: IPv6 single stack support) posted (#2) for review on master by Kevin Vigor (kvigor)
REVIEW: https://review.gluster.org/16228 (gluster: IPv6 single stack support) posted (#3) for review on master by Kevin Vigor (kvigor)
REVIEW: https://review.gluster.org/16228 (gluster: IPv6 single stack support) posted (#4) for review on master by MOHIT AGRAWAL (moagrawa)
REVIEW: https://review.gluster.org/16228 (gluster: IPv6 single stack support) posted (#5) for review on master by MOHIT AGRAWAL (moagrawa)
REVIEW: https://review.gluster.org/16228 (gluster: IPv6 single stack support) posted (#6) for review on master by MOHIT AGRAWAL (moagrawa)
COMMIT: https://review.gluster.org/16228 committed in master by Amar Tumballi (amarts) ------ commit 1260ee53b1674234e6f083563bdcd258e46a6faa Author: Kevin Vigor <kvigor> Date: Fri Apr 28 16:44:29 2017 -0700 gluster: IPv6 single stack support Summary: - This diff changes all locations in the code to prefer inet6 family instead of inet. This will allow change GlusterFS to operate via IPv6 instead of IPv4 for all internal operations while still being able to serve (FUSE or NFS) clients via IPv4. - The changes apply to NFS as well. - This diff ports D1892990, D1897341 & D1896522 to the 3.8 branch. Test Plan: Prove tests! Reviewers: dph, rwareing Signed-off-by: Shreyas Siravara <sshreyas> Change-Id: I34fdaaeb33c194782255625e00616faf75d60c33 BUG: 1406898 Reviewed-on-3.8-fb: http://review.gluster.org/16059 Reviewed-by: Shreyas Siravara <sshreyas> Tested-by: Shreyas Siravara <sshreyas>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report. glusterfs-3.13.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/