Bug 1277054 - peer probe using IPv6 not working
Summary: peer probe using IPv6 not working
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: GlusterFS
Classification: Community
Component: transport
Version: mainline
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Atin Mukherjee
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-02 08:40 UTC by Bishoy Mikhael
Modified: 2019-05-09 09:55 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-09 09:55:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Bishoy Mikhael 2015-11-02 08:40:05 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
3.7.x


How reproducible:
Always

Steps to Reproduce:
1. peer probe using IPv6 address


Actual results:
peer probe: failed: Probe returned with Transport endpoint is not connected

Expected results:
peer probe: success.

Additional info:
When you try to peer probe using IPv6 address, it fails.

The logs show the following error:

E [MSGID: 101075] [common-utils.c:306:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known)
E [name.c:247:af_inet_client_get_remote_sockaddr] 0-management: DNS resolution failed on host xxxxxxxxxxxxx
Comment 1 Amar Tumballi 2019-05-09 09:55:35 UTC 
Please try version 6.x and we have fixed some of the ipv6 issues in cli/glusterd and in other places.
Note You need to log in before you can comment on or make changes to this bug.