Bug 1343946

Summary:	[gluster]: geo-rep creation fails and status goes to UNKNOWN
Product:	[oVirt] ovirt-engine	Reporter:	Sahina Bose <sabose>
Component:	BLL.Gluster	Assignee:	Ramesh N <rnachimu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	3.6.0	CC:	bmcclain, bugs, eedri, knarra, sabose
Target Milestone:	ovirt-3.6.7	Keywords:	Regression, ZStream
Target Release:	3.6.7.3	Flags:	rule-engine: ovirt-3.6.z+ rule-engine: blocker+ bmcclain: planning_ack+ sabose: devel_ack+ knarra: testing_ack+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-3.6.7.4	Doc Type:	Bug Fix
Doc Text:	Cause: There is a change in gluster cli output for 'gep rep status'. Slave volume ID is added to geo rep session key. Consequence: Gluster Geo-Rep session key parsing was failing and resulted in Geo Rep session status being shown as 'UNKNOWN' Fix: Update Gluster Geo-Rep session key parsing logic in Ovirt and VDSM to handle the change in Gluster CLI. Result: Gluster geo-rep sessions can be created from Ovirt.	Story Points:	---
Clone Of:	1343650	Environment:
Last Closed:	2016-07-04 12:31:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1348057
Bug Blocks:

Description Sahina Bose 2016-06-08 11:41:51 UTC

+++ This bug was initially created as a clone of Bug #1343650 +++

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.


--- Additional comment from Ramesh N on 2016-06-08 00:28:15 EDT ---

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 1 Red Hat Bugzilla Rules Engine 2016-06-08 11:41:55 UTC

This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Eyal Edri 2016-06-23 11:58:58 UTC

Sahina, does this bug requires vdsm-gluster for verification?
If it does, it can only be verified with oVirt 3.6.7 rpms.

Comment 3 Ramesh N 2016-06-23 12:09:03 UTC

Yes. It requires the vdsm-gluster-4.17.32-0.el7.centos.noarch.rpm  in 
http://resources.ovirt.org/pub/ovirt-3.6-pre/rpm/el7/noarch/

Comment 4 SATHEESARAN 2016-06-28 02:24:02 UTC

Tested with RHEV 3.6.7.5 and vdsm-4.17.31-0.2.el7ev.noarch

Geo-rep session shows the correct status while geo-rep session is created from gluster CLI