Bug 1688239

Summary:	geo-rep session creation fails with IPV6
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhhiv-1.6	CC:	csaba, dwalveka, khiremat, pasik, rcyriac, rhs-bugs, sabose, seamurph, sheggodu, storage-qa-internal
Target Milestone:	---
Target Release:	RHHI-V 1.8
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	rhvh-4.4.1	Doc Type:	Bug Fix
Doc Text:	Previously, geo-replication could not be used with IPv6 addresses. With this release, all the helper scripts used for gluster geo-replication are made compatible with IPV6 hostnames(FQDN).	Story Points:	---
Clone Of:	1688231	Environment:
Last Closed:	2020-08-04 14:50:55 UTC	Type:	---
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:	1688231, 1688833, 1695436
Bug Blocks:	1683647, 1779975

Description SATHEESARAN 2019-03-13 11:49:58 UTC

Description of problem:
-----------------------
This issue is seen with the RHHI-V usecase. VM images are stored in the gluster volumes and geo-replicated to the secondary site, for DR use case.

When IPv6 is used, the additional mount option is required --xlator-option=transport.address-family=inet6". But when geo-rep check for slave space with gverify.sh, these mount options are not considered and it fails to mount either master or slave volume

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHGS 3.4.4 ( glusterfs-3.12.2-47 )

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Create geo-rep session from the master to slave

Actual results:
--------------
Creation of geo-rep session fails at gverify.sh

Expected results:
-----------------
Creation of geo-rep session should be successful

Comment 1 SATHEESARAN 2019-03-19 09:53:10 UTC

This issue will be marked down as a limitation with IPV6 support, removing the release_blocker flag set on this bug

Comment 2 Yaniv Kaul 2019-03-27 11:29:38 UTC

I thought we pushed this functionality into batch update 4?

Comment 3 Sahina Bose 2019-03-27 11:49:15 UTC

(In reply to Yaniv Kaul from comment #2)
> I thought we pushed this functionality into batch update 4?

No, it did not make it to 3.4.4, the RHGS bug is moved to 3.5

Comment 5 Sahina Bose 2019-03-29 13:47:31 UTC

Redirecting needinfo to SME

Comment 11 SATHEESARAN 2020-07-16 10:37:36 UTC

Tested with RHVH 4.4.1

1. Created the master cluster with IPV6 only enabled ( hosts are using FQDN )
2. Create the geo-rep slave also with IPV6 only ( hosts are using FQDN )
3. Start the geo-rep session
4. Post sync, all the files on VMs running on master site are synced to slave site

Comment 15 errata-xmlrpc 2020-08-04 14:50:55 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (RHHI for Virtualization 1.8 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:3314