Bug 1582564

Summary:	Using a new device for creating non vdo volume is being blocked
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	bipin <bshetty>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhhiv-1.5	CC:	rcyriac, rhs-bugs, sabose, sankarshan
Target Milestone:	---
Target Release:	RHHI-V 1.5
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1582579 (view as bug list)		Environment:
Last Closed:	2019-05-20 04:55:07 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:	1582579
Bug Blocks:	1520836

Description bipin 2018-05-25 15:22:58 UTC

Description of problem:

Currently  using a device for creating a non VDO volume is not possible.If we check any other device which has the VDO volume , even the device which is used to create a non VDO volume is also geting checked. So unchecking this non VDO volume device unchecks the VDO volume device as well.



Version-Release number of selected component (if applicable):
gdeploy-2.0.2-27.el7rhgs.noarch
ansible-2.5.3-1.el7ae.noarch
cockpit-ovirt-dashboard-0.11.25-1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Start the gluster deployment
2. Use two different device for creating VDO and non-VDO volume (eg: /dev/sdb /dev/sdc)
3. Check the bricks under sdb , then the bricks under sdc are also getting checked

Actual results:
All the devices selected are getting checked

Expected results:
Should not check automatically unless the brick are in the same device

Additional info:


Have attached the screenshot

Comment 5 bipin 2018-07-03 08:27:02 UTC

Moving the bug as verified. Tested in version cockpit-ovirt-dashboard-0.11.28