Bug 1224697

Summary:	[New] - UI does not list the config option 'use_meta_volume' to start a new geo rep session.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	rhsc	Assignee:	anmol babu <anbabu>
Status:	CLOSED ERRATA	QA Contact:	Arthy Loganathan <aloganat>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.1	CC:	asrivast, dpati, nlevinki, rhs-bugs, sabose
Target Milestone:	---
Target Release:	RHGS 3.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhsc-3.1.0-59	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-29 05:29:38 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:	1202842, 1224288

Description RamaKasturi 2015-05-25 11:40:14 UTC

Description of problem:
UI does not list any option called use_meta_volume to start a new geo rep session.

Version-Release number of selected component (if applicable):
rhsc-3.1.0-0.0.scratch.master.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a new geo rep session from the UI.
2. Now check for the config option use_meta_volume.
3.

Actual results:
UI does  not list any config option called use_meta_volume.

Expected results:
use_meta_volume should be listed in the UI as config option because it is always recommended to use this volume to work with geo-replication from everglades.

Additional info:

Comment 2 Sahina Bose 2015-06-01 08:48:57 UTC

Seed the config option in DB for engine to pick this up

Comment 5 Ramesh N 2015-06-15 05:39:59 UTC

Moving back to MODIFIED as the build is not ready but errata has moved the bugs to ON_QA.

Comment 6 Arthy Loganathan 2015-06-19 09:05:47 UTC

Verified the fix in build,
rhsc-3.1.0-0.60.el6.noarch

use_meta_volume option is present in geo replication config options tab.

Comment 8 errata-xmlrpc 2015-07-29 05:29:38 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://rhn.redhat.com/errata/RHEA-2015-1494.html