Bug 1191072

Summary:	ipv6 enabled on the peer, but dns resolution fails with ipv6 and gluster does not fall back to ipv4
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	rpc	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	atumball, bugs, mchangir, ndevos, pcuzner, rgowdapp
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	rpc-3.4.0?
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1190551	Environment:
Last Closed:	2019-07-02 04:46:49 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:
Bug Depends On:
Bug Blocks:	1190551, 1309178

Description Niels de Vos 2015-02-10 12:38:00 UTC

+++ This bug was initially created as a clone of Bug #1190551 +++
+++                                                           +++
+++ Use this bug to get a fix in the master branch.           +++
+++                                                           +++

Description of problem:
Using gluster with ovirt as a hyperconverged platform based on rhel7. by default rhel7 has ipv6 enabled. during configuration I see address resolution failures preventing ovirt hosted-engine deployment from working.


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

glusterfs 3.6.2
ovirt 3.5
ovirt-hosted-engine-setup (from Sandro Bonazzola - 1.2.2)

How reproducible:
When ipv6 is enabled this happens every time hosted-engine --deploy is attempted

Steps to Reproduce:
1. have dns resolution working for ipv4 only
2. configure gluster (peers and volume)
3. attempt to run hosted-engine --deploy (with ipv6 enabled on the host)


Actual results:
[ INFO  ] Waiting for VDSM hardware info
[ INFO  ] Waiting for VDSM hardware info
[ INFO  ] Configuring the management bridge
[ ERROR ] Failed to execute stage 'Misc configuration': Connection to storage server failed
[ INFO  ] Stage: Clean up
[ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20150203193700.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination

snip from glusterd log file
[2015-02-04 00:36:59.996195] E [common-utils.c:227:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known)
[2015-02-04 00:36:59.996292] E [name.c:242:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host gprfc085-glfs.rhev-rhss.lab


Expected results:
If ipv6 is enabled, but DNS does not return an ipv6 entry, retry with ipv6 - only fail the request if lookups to both ipv6 and ipv4 fail.

Additional info:
Workaround was to disable ipv6 on the host - subsequent lookups are ipv4 only and name resoltion works as expected.

log for the storage domain that was attempted to be located is atteched - timestamp - 2015-02-04 00:36:39.959656

Comment 1 Milind Changire 2019-01-07 03:51:01 UTC

Patch [1] is being worked on to provide ipv6 peer configuration and communication.
However, mixed mode (ipv4 and ipv6) communication will still not be possible.

1. https://review.gluster.org/c/glusterfs/+/21948

Comment 2 Yaniv Kaul 2019-04-17 09:55:34 UTC

Same fate as https://bugzilla.redhat.com/show_bug.cgi?id=1190551 ?

Comment 3 Niels de Vos 2019-04-26 06:09:07 UTC

I think we still want fix this is upcoming versions. Milind, could you close this BZ if it is not the case?

Comment 4 Milind Changire 2019-04-26 06:12:15 UTC

Forwarding needinfo to Raghavendra G.

Comment 5 Amar Tumballi 2019-07-02 04:46:49 UTC

Mixed mode is not a focus right now. And glusterfs-6.x is known to have complete IPv6 support.