[Bugs] [Bug 1635863] New: Gluster peer probe doesn't work for IPv6

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1635863

            Bug ID: 1635863
           Summary: Gluster peer probe doesn't work for IPv6
           Product: GlusterFS
           Version: 4.1
         Component: rpc
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: y.zhao at nokia.com
                CC: bugs at gluster.org



Description of problem:

# gluster peer probe gluster-1
peer probe: failed: Probe returned with Transport endpoint is not connected

Version-Release number of selected component (if applicable):
# gluster peer probe gluster-1
peer probe: failed: Probe returned with Transport endpoint is not connected


How reproducible:
Install 4.1.4 and run gluster peer probe ipv6-peer

Steps to Reproduce:
1. turn on "option transport.address-family inet6" in glusterd.vol
2. Verify the remote peer is ping6-able
3. Run "gluster peer probe"

Actual results:

# gluster peer probe gluster-1
peer probe: failed: Probe returned with Transport endpoint is not connected
# ping6 gluster-1
PING gluster-1(gluster-1 (3010::13:199:0:0:42)) 56 data bytes
64 bytes from gluster-1 (3010::13:199:0:0:42): icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from gluster-1 (3010::13:199:0:0:42): icmp_seq=2 ttl=64 time=0.439 ms


Expected results:
Peer probe should succeeds.

Additional info:

1). Log from glusterd.log

[2018-10-03 19:06:25.009874] I [MSGID: 106487]
[glusterd-handler.c:1244:__glusterd_handle_cli_probe] 0-glusterd: Received CLI
probe req gluster-1 24007
[2018-10-03 19:06:25.010729] I [MSGID: 106128]
[glusterd-handler.c:3635:glusterd_probe_begin] 0-glusterd: Unable to find
peerinfo for host: gluster-1 (24007)
[2018-10-03 19:06:25.028897] W [MSGID: 106061]
[glusterd-handler.c:3408:glusterd_transport_inet_options_build] 0-glusterd:
Failed to get tcp-user-timeout
[2018-10-03 19:06:25.029031] I [rpc-clnt.c:1059:rpc_clnt_connection_init]
0-management: setting frame-timeout to 600
[2018-10-03 19:06:25.033267] E [MSGID: 101075]
[common-utils.c:312:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or
service not known)
[2018-10-03 19:06:25.033366] E [name.c:267:af_inet_client_get_remote_sockaddr]
0-management: DNS resolution failed on host gluster-1
[2018-10-03 19:06:25.033538] I [MSGID: 106498]
[glusterd-handler.c:3561:glusterd_friend_add] 0-management: connect returned 0
[2018-10-03 19:06:25.033657] I [MSGID: 106004]
[glusterd-handler.c:6382:__glusterd_peer_rpc_notify] 0-management: Peer
<gluster-1> (<00000000-0000-0000-0000-000000000000>), in state <Establishing
Connection>, has disconnected from glusterd.

2). Peer probe works for ipv4 address with the same config

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.