Bug 1343650

Summary: [geo-rep+rhsc]: geo-rep creation fails and status goes to UNKNOWN with latest build
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Sachin <sashinde>
Component: rhscAssignee: Ramesh N <rnachimu>
Status: CLOSED ERRATA QA Contact: RHS-C QE <rhsc-qe-bugs>
Severity: urgent Docs Contact:
Priority: high    
Version: rhgs-3.1CC: amukherj, mzywusko, rcyriac, rhinduja, rhs-bugs, rnachimu, sabose
Target Milestone: ---Keywords: Regression, ZStream
Target Release: RHGS 3.1.3   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rhsc-3.1.3-73 , vdsm-4.16.30-1.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1343946 (view as bug list) Environment:
Last Closed: 2016-06-23 05:28:01 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: 1311817    

Description Sachin 2016-06-07 15:09:29 UTC
Description of problem:
=======================

With the latest build, the creation of geo-replication fails and status goes to unknown state. Also, setting up the configuration (like use_meta_volume true) also fails.

This has worked with earlier 3.1.3 builds: glusterfs-3.7.9-4. Screenshot and logs will be updated. 


Version-Release number of selected component (if applicable):
=============================================================
RHSC: 3.1.3-0.72.el6
GLusterfs: glusterfs-3.7.9-8


How reproducible:
=================
Always


Steps to Reproduce:
===================
1. From UI, Setup master and slave cluster
2. Create Master and Slave volume
3. Setup Geo-Rep between Master and Slave Volume

Actual results:
===============

Geo-Rep goes to UNKNOWN State. Also, setting up any config option fails.


Expected results:
================

Geo-Replication should be successful

Additional Info:
================

With Same RHSC Version: 3.1.3-0.72.el6 and older gluster version: glusterfs-3.7.9-4, it works.

Comment 9 Ramesh N 2016-06-08 04:28:15 UTC
This bug is a result of a recent change in gluster cli output for 'gep rep status'. Slave volume ID is added to geo rep session key. We have to change our gluster CLI output parsing in VDSM and RHSC.

Old Geo rep Session Key: 'b1b92a4e-ce58-4b9d-ac3b-a8c693bca029:ssh://10.70.37.190::slave'

New Geo rep Session Key: 'b1b92a4e-ce58-4b9d-ac3b-a8c693bca029:ssh://10.70.37.190::slave:bd52ddf1-9659-4168-8197-c62e9f3e855c'

Comment 15 Sachin 2016-06-10 10:08:26 UTC
Verified the fix and moving the bug to verified state.

-Sachin

Comment 17 errata-xmlrpc 2016-06-23 05:28:01 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, 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/RHBA-2016:1242