Bug 1749387

Summary:	The default glusterfs client is not initiating AAAA resolution for IPv6 based glusterfs servers and hence could not connect
Product:	[Community] GlusterFS	Reporter:	Ppal <prab.bangalore>
Component:	unclassified	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6	CC:	bugs, moagrawa, rhs-bugs, vbellur, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-24 06:33:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ppal 2019-09-05 13:59:47 UTC

Trying to connect to a glusterfs server running over IPv6. Glusterfs fuse was not able to connect to the glusterfs server. TCP dump revealed that DNS queries are initiated only for A records (IPv4) and not for AAAA record (IPv6). 

It is possible that the glusterfs client needs to be separately rebuilt for IPv6 with --with-ipv6-default  option set. But could not fund a glusterfs client debian which is built for IPv6. 

Do we need separate glusterfs binary or is there a CLI option to connect to IPv6 without rebuilding the glusterfs binary with --with-ipv6-default  flag?

Comment 2 Ppal 2019-09-05 14:01:29 UTC

Running glusterfs 6.5

Comment 4 Nithya Balachandran 2019-11-05 10:38:20 UTC

(In reply to Ppal from comment #2)
> Running glusterfs 6.5

As this is an upstream release, changing the product accordingly.

Comment 5 Mohit Agrawal 2020-02-24 06:33:21 UTC

You can mount the volume after using the command-language argument -o xlator-option="transport.address-family=inet6" to connect with the volume on IPV6.You have to change the default address address-family also to inet6 in /etc/glusterfs/glusterd.vol to mount the volume successfully.


The issue is already fixed from the patch (https://review.gluster.org/#/c/glusterfs/+/21948/) and a patch is already merged in releases so I am closing the bug.

Please reopen it if you face any issue.

Thanks,
Mohit Agrawal