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

Bug 1195699

Summary:	[New] - Geo-replication status is shown as 'UNKNOWN' in the UI.
Product:	[oVirt] ovirt-engine	Reporter:	RamaKasturi <knarra>
Component:	Frontend.WebAdmin	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RamaKasturi <knarra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	bugs, gklein, knarra, lsurette, mgoldboi, rbalakri, sabose, yeylon, ykaul
Target Milestone:	ovirt-3.6.0-rc	Flags:	rule-engine: ovirt-3.6.0+ ylavi: planning_ack+ rule-engine: devel_ack+ sasundar: testing_ack+
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-3.6.0-0.0.master.20150518173633.gitcf0f078	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1224277 (view as bug list)		Environment:
Last Closed:	2016-02-10 12:57:14 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:	1187461, 1224277

Description RamaKasturi 2015-02-24 12:32:06 UTC

Description of problem:
When geo-rep sessions are active / stopped, status field in UI reflects as "UNKNOWN"

Version-Release number of selected component (if applicable):
ovirt-engine-3.6.0-0.0.master.20150219124503.gitafae793.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create two clusters master and slave and manage it through console.
2. Create two volumes i.e one in master and one in slave.
3. start the geo-replication from CLI by running the command "gluster vol geo <vol1> <slaveip>::<vol2> start
4. Click on the geo-replication subtab in the volumes and click on 'sync'

Actual results:
geo-rep sessions gets synced from CLI , but the status is shown as 'UNKNOWN' when the sessions are active and stopped.

Expected results:
Geo-rep sessions should reflect correct status in the UI.

Additional info:

Comment 1 Sahina Bose 2015-02-25 06:55:25 UTC

Could you provide the output of "gluster volume geo status"

Comment 3 RamaKasturi 2015-04-15 06:24:19 UTC

I still see this issue i.e the status not being synced properly. Moving this bug back to assigned.


Attaching the engine and vdsm logs for the same. Logs can be found in the link below.

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1205544/

Comment 4 Sahina Bose 2015-05-04 07:25:56 UTC

Patch posted to handle changes in geo-rep status from gluster

Comment 5 RamaKasturi 2016-02-03 07:17:57 UTC

Tested with RHEV 3.6.2.6 and RHGS Nightly ( glusterfs-3.7.5-17.el7rhgs )

UI is able to sync the geo-rep session successfully when it is created from CLI.