Bug 1955990

Summary: [GSS] Geo-rep won't start after upgrade to rhgs 3.5.3
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: slenzen
Component: geo-replicationAssignee: Shwetha K Acharya <sacharya>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Vinayak Papnoi <vpapnoi>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: amanzane, amark, amenon, csaba, khiremat, mduasope, psony, rhs-bugs, sabose, sacharya, sajmoham, saraut, sheggodu, vdas, vpapnoi
Target Milestone: ---Flags: mduasope: needinfo-
mduasope: needinfo-
mduasope: needinfo-
mduasope: needinfo-
ssivakum: needinfo-
ssivakum: needinfo-
amanzane: needinfo-
amanzane: needinfo-
mduasope: needinfo-
mduasope: needinfo-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-18 10:41:38 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 slenzen 2021-05-01 23:35:58 UTC 
Before you record your issue, ensure you are using the latest version of Gluster.

Provide version-Release number of selected component (if applicable): glusterfs-geo-replication-6.0-49.el7rhgs.x86_64

 
Have you searched the Bugzilla archives for same/similar issues reported. yes


 
Have you discovered any workarounds?. If not, Read the troubleshooting documentation to help solve your issue. ( https://mojo.redhat.com/groups/gss-gluster (Gluster feature and its troubleshooting)  https://access.redhat.com/articles/1365073 (Specific debug data that needs to be collected for GlusterFS to help troubleshooting)

None available.


Describe the issue:(please be detailed as possible and provide log snippets) Customer upgraded to RHGS 3.5.3 but geo-replication would not start after the upgrade. It was recommended to recreate the sessions to help correct the issue. After following the steps in our documentation located here: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5/html-single/administration_guide/index#Setting_Up_the_Environment_for_a_Secure_Geo-replication_Slave

geo-replication status would only report a status of created.



Is this issue reproducible? If yes, share more details.: N/A

 
Mandatory Information for all Bugs: Will add in next private comment

1 - gluster v <volname> info
2 - gluster v <volname> heal info
3 - gluster v <volname> status
4 - Fuse Mount/SMB/nfs-ganesha/OCS ???
 
Additional info: N/A