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

Bug 1196092

Summary:	[New] - Add the SLAVE USER column to geo-rep status output.
Product:	[Retired] oVirt	Reporter:	RamaKasturi <knarra>
Component:	ovirt-engine-webadmin	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RamaKasturi <knarra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.6	CC:	bugs, ecohen, gklein, lsurette, mgoldboi, rbalakri, sabose, yeylon
Target Milestone:	---
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	gluster
Fixed In Version:	ovirt-engine-3.6.0-0.0.master.20150515172356.git426b5a1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-04 13:43:50 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

Description RamaKasturi 2015-02-25 09:51:03 UTC

Description of problem:
Columns "DESTINATION HOST", "DESTINATION VOLUME" and STATUS is displayed in the geo-replication subtab of the volumes. In addition to that display the column "SLAVE USER" as well.

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

How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:
As of now there is no column called SLAVE USER in the geo-rep status output in UI.

Expected results:
Another column called 'SLAVE_USER' should be displayed in the status output of geo-rep in the UI.

Additional info:

Comment 1 RamaKasturi 2015-05-20 05:59:39 UTC

Verified and works fine with build ovirt-engine-3.6.0-0.0.master.20150517172245.git089e126.el6.noarch.

There is a new column called User Name added in the geo-rep status output in UI.

Comment 2 Sandro Bonazzola 2015-11-04 13:43:50 UTC

oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.