Bug 1566448

Summary:	Enable lvmcache on all the hosts, when enabled on one of the them
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:	bshetty, godas, rhs-bugs
Target Milestone:	---
Target Release:	RHHI-V 1.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1566450 (view as bug list)		Environment:
Last Closed:	2018-11-08 05:38:52 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:	1566450
Bug Blocks:	1520836

Description SATHEESARAN 2018-04-12 10:47:36 UTC

Description of problem:
-----------------------
With the existing design, user needs to enable lvmcache for each of the host. It will be helpful, if the lvmcache is enabled on one of the host, it should be automagically enabled on rest of the hosts listed in the UI.

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
cockpit-ovirt-dashboard-0.11.20-1.el7ev.noarch

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

Steps to Reproduce:
-------------------
1. Start RHHI 2.0 deployment using cockpit
2. On the bricks tab, enable lvmcache on one of the host
3. Check whether all the hosts has this lvmcache enabled

Actual results:
---------------
lvmcache is not enabled on other hosts

Expected results:
-----------------
lvmcache when enabled on one of the hosts, should be enabled on all the hosts

Comment 4 bipin 2018-05-31 13:31:38 UTC

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

Comment 8 errata-xmlrpc 2018-11-08 05:38:52 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