[Bugs] [Bug 1310445] Gluster not resolving hosts with IPv6 only lookups
bugzilla at redhat.com
bugzilla at redhat.com
Sun Mar 20 14:34:17 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1310445
--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13787 committed in release-3.7 by Atin
Mukherjee (amukherj at redhat.com)
------
commit b33f3c95ec9c8112e6677e09cea05c4c462040d0
Author: Nithin D <nithind1988 at yahoo.in>
Date: Sun Feb 28 21:45:48 2016 +0530
glusterd: Bug fixes for IPv6 support
Backport of http://review.gluster.org/#/c/11988/
Problem:
Glusterd not working using ipv6 transport. The idea is with proper
glusterd.vol configuration,
1. glusterd needs to listen on default port (240007) as IPv6 TCP listner.
2. Volume creation/deletion/mounting/add-bricks/delete-bricks/peer-probe
needs to work using ipv6 addresses.
3. Bricks needs to listen on ipv6 addresses.
All the above functionality is needed to say that glusterd supports ipv6
transport and this is broken.
Fix:
When "option transport.address-family inet6" option is present in
glusterd.vol
file, it is made sure that glusterd creates listeners using ipv6 sockets
only and also the same information is saved
inside brick volume files used by glusterfsd brick process when they are
starting.
Tests Run:
Regression tests using ./run-tests.sh
IPv4: Regression tests using ./run-tests.sh for release-3.7 branch verified
by comparing with clean repo.
IPv6: (Need to add the above mentioned config and also add an entry for
"hostname ::1" in /etc/hosts)
Started failing at ./tests/basic/glusterd/arbiter-volume-probe.t and
ran successfully till here
Change-Id: Idd7513aa2347ce0de2b1f68daeecce1b7a39a7af
BUG: 1310445
Signed-off-by: Nithin D <nithind1988 at yahoo.in>
Reviewed-on: http://review.gluster.org/13787
Smoke: Gluster Build System <jenkins at build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Ssfd5apXKP&a=cc_unsubscribe
More information about the Bugs
mailing list