Bug 1547450

Summary:	create one VDO volume when encryption & dedupe enabled on few or all the bricks on the same device
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhhiv-1.5	CC:	rhs-bugs
Target Milestone:	---
Target Release:	RHHI-V 1.5
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.11.16-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1547453 (view as bug list)		Environment:
Last Closed:	2018-11-08 05:37:26 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:	1547453
Bug Blocks:	1520836

Description SATHEESARAN 2018-02-21 11:03:58 UTC

Description of problem:
-----------------------
User can enable dedupe & compression on select few or all the bricks on the same device. Currently the dedupe & compression will be enabled on all the bricks, that are created on the same device.

But when the user has chosen to enable dedupe & compression on 2 bricks from the same device, 2 different VDO volumes are created.

When the user has chosen to enable dedupe & compression on 3 bricks ( engine, vmstore, data ) from the same device, 3 different VDO volumes are created.

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

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Start RHHI installation from cockpit using 'Hosted Engine with Gluster' 
2. On the bricks tab (4th tab), select 'Enable Dedupe & Compression' on all the 3 bricks
3. Observe the generated gdeploy config file

Actual results:
---------------
1. Generated gdeploy config file has sections to create 3 different VDO volumes
2. Name of VDO volume is not generic

Expected results:
-----------------
1. Generated gdeploy config file should have sections to create only one VDO volume
2. Name of the VDO volume should be generic corresponding to the device (e.g)vdovolume_sdb

Comment 1 SATHEESARAN 2018-02-21 11:16:43 UTC

Additional info:
----------------
Following is the snip of config file with dedupe & compression enabled on all the 3 bricks (ie.) engine, data, vmstore

[vdo]
action=create
devices=sdb,sdb,sdb
names=engine,data,vmstore
logicalsize=400,2000,2000

Following is the snip of config file with dedupe & compression enabled on all the 2 bricks (ie.) engine, data

[vdo]
action=create
devices=sdb,sdb
names=engine,data
logicalsize=400,2000

Irrespective of dedupe and compression enabled 1 or 2 or 3 bricks, the expected conf file should be:

[vdo]
action=create
devices=sdb
names=vdovol_sdb
logicalsize=<size>

Comment 5 SATHEESARAN 2018-04-25 10:29:06 UTC

Tested with cockpit-ovirt-dashboard-0.11.22
There is only VDO volume created for all the bricks.

Comment 7 errata-xmlrpc 2018-11-08 05:37:26 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://access.redhat.com/errata/RHEA-2018:3523