Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1348057

Summary:	Geo-replication sync broken due to change in gluster CLI
Product:	[oVirt] vdsm	Reporter:	Sahina Bose <sabose>
Component:	Gluster	Assignee:	Ramesh N <rnachimu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	4.17.31	CC:	bugs, eedri, ylavi
Target Milestone:	ovirt-3.6.7	Flags:	rule-engine: ovirt-3.6.z+ rule-engine: blocker+ ylavi: planning_ack+ sabose: devel_ack+ sasundar: testing_ack+
Target Release:	4.17.32
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	vdsm-4.17.32	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-04 12:32:40 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:
Bug Blocks:	1343946

Description Sahina Bose 2016-06-20 04:28:51 UTC

Description of problem:

Monitoring and management of geo-replication via vdsm is broken, as the information returned by vdsm is incorrect. The parsing logic is broken due to the change in gluster cli output

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a geo-rep session from engine.

Actual results:
Session status is changed to UNKNOWN

Expected results:

Session status is reflected and further actions possible


Additional info:

Comment 1 Sahina Bose 2016-06-20 04:36:17 UTC

This is required for HC use case to monitor the geo-replication for DR workflow

Comment 2 Eyal Edri 2016-06-23 11:57:12 UTC

fyi, please use VDSM from latest oVirt 3.6.7 to verify this.
you can find the rpms here:
http://resources.ovirt.org/pub/ovirt-3.6-pre/rpm/el7/noarch/

Comment 4 SATHEESARAN 2016-06-28 02:25:44 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