Bug 1573473

Summary:	The VDO logical size check in box should be enabled automatically in all hosts
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:	medium
Version:	0.11.7	CC:	bugs, rhs-bugs, sabose, sankarshan, sasundar
Target Milestone:	ovirt-4.2.4	Flags:	rule-engine: ovirt-4.2? bshetty: planning_ack? rule-engine: devel_ack+ bshetty: testing_ack+
Target Release:	0.11.25
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.11.25-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1573472	Environment:
Last Closed:	2018-06-26 08:37:02 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:	1573472, 1582207

Description bipin 2018-05-01 11:50:17 UTC

+++ This bug was initially created as a clone of Bug #1573472 +++

Description of problem:
Currently when we check the "enable Dedupe and Compression" (VDO) button its enables only for the particular device in the host. Need to implemement in such a way that it should be enabled in all the hosts automatically when enabled on  one host.


Version-Release number of selected component (if applicable):
cockpit-ovirt-dashboard-0.11.23-1.el7ev.noarch
gdeploy-2.0.2-26.el7rhgs.noarch

How reproducible:


Steps to Reproduce:
1. Login to cockpit
2. Start gluster deployment
3. Check the "enable Dedupe and Compression" box

Actual results:
Doesn't enable for devices in other hosts


Expected results:
should automatically enable for devices in other hosts

Additional info:

Comment 1 bipin 2018-05-31 15:52:26 UTC

Verified the bug with latest cockpit-ovirt-dashboard-0.11.25-1.

Attaching the screenshot

Comment 4 Sandro Bonazzola 2018-06-26 08:37:02 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.