Bug 1582579

Summary:	Using a new device for creating non vdo volume is being blocked
Product:	[oVirt] cockpit-ovirt	Reporter:	bipin <bshetty>
Component:	Gdeploy	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bipin <bshetty>
Severity:	high	Docs Contact:
Priority:	high
Version:	0.11.7	CC:	bugs, godas, rhs-bugs, sabose, sankarshan, sasundar
Target Milestone:	ovirt-4.2.4	Flags:	sabose: ovirt-4.2? sabose: blocker? bshetty: planning_ack? rule-engine: devel_ack+ sasundar: testing_ack+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.11.28-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1582564	Environment:
Last Closed:	2018-06-26 08:35:35 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:	1582207, 1582564

Comment 2 SATHEESARAN 2018-05-31 12:51:16 UTC

After conversing with Gobinda, this looks like a known design issue that either customer can create VDO enabled volumes or volumes without dedupe & compression.

This might not be useful for some scenarios. For instance, if the customer/user wants to create couple of volumes, one replica 3 volume with dedupe & compression enabled , and other arbitrated replicate volume, and doesn't want to enable to dedupe & compression on the arbiter bricks, this will not help.

This is a blocker in those cases.

@Sahina, what do you think ?

Comment 3 SATHEESARAN 2018-06-02 02:43:23 UTC

Also noticed that the mix of volumes with compression&dedupe enabled and disabled can't be created during RHHI deployment. This also seem to be a problem

Comment 4 Sahina Bose 2018-06-06 11:32:13 UTC

Yes, we should be allowing a mix of deduped/non-deduped devices as long as the devices are different.
Gobinda, can this be addressed?

Comment 6 Gobinda Das 2018-06-06 12:08:51 UTC

Sahina,
 I am checking and will update.

Comment 7 bipin 2018-06-19 07:03:24 UTC

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

Comment 8 Sandro Bonazzola 2018-06-26 08:35:35 UTC

This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.