Bug 1855965

Summary: [IPV6] RHHI-V geo-replication fails to start sync with IPV6 address
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Gobinda Das <godas>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhhiv-1.7CC: rhs-bugs
Target Milestone: ---Keywords: ZStream
Target Release: RHHI-V 1.8.z Batch Update 2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-6.0-41 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1855966 (view as bug list) Environment:
Last Closed: 2020-12-01 06:58:36 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: 1855966    
Bug Blocks:    

Description SATHEESARAN 2020-07-11 11:39:27 UTC 
Description of problem:
-----------------------
Geo-replication session was established with IPV6 hostnames, but when starting the geo-rep session, it never starts

Version-Release number of selected component (if applicable):
---------------------------------------------------------------
RHHI-V 1.8
RHGS 3.5.2 ( glusterfs-6.0-37.1.el8rhgs )
glusterfs-geo-replication-6.0-37.1.el8rhgs 

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

Steps to Reproduce:
-------------------
1. Establish the geo-rep session from master to slave, both master and slave are using IPV6, but no IPv4.
2. Start the session

Actual results:
-----------------
Session fails to start, remains in geo-rep session remains created state

Expected results:
-----------------
Session should start sync from master to slave


Additional info:
Comment 1 SATHEESARAN 2020-07-12 13:56:35 UTC 
Patch https://review.gluster.org/#/c/glusterfs/+/24706/ is posted upstream
Comment 2 SATHEESARAN 2020-07-13 10:14:26 UTC 
This issue is not a blocker for RHHI-V 1.8

This issue is seen only with the direct usage of IPV6 addresses and
not with IPV6 hostnames

RHHI-V highly recommends usage of IPV6 hostnames and not direct IPV6 addresses.
So this issue can be tracked with RHGS 3.5.3
Comment 5 SATHEESARAN 2020-11-02 08:05:37 UTC 
Tested with glusterfs-6.0-46.el8rhgs and found that files are synced to the secondary volume,
when the geo-rep session is configured with IPv4 addresses


Here are the much detailed information about the test
0. Created the primary cluster with FQDNs and enabled cluster.enable-shared-storage that creates the gluster-shared-storage volume for meta operations
1. Created the source/primary volume with FQDN on the primary cluster
2. Created the destination/secondary cluster and volume with IPv4
3. Mounted the primary volume on the primary cluster, and created few files on the fuse mounted volume
4. Created the geo-rep session from primary to secondary volume using IPs on the secondary host
5. Configured the geo-rep session to make use of meta volume
6. Started the session
7. Followed up the geo-rep status to make sure, that the sync is completed
8. Mounted the volume on the secondary cluster, and compared the sha256sum on the primary volume and that matched