Bug 1855756

Summary: auto-populate LV cache size for other hosts during deployment
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Gobinda Das <godas>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: rhs-bugs
Target Milestone: ---Keywords: ZStream
Target Release: RHHI-V 1.8.z Batch Update 1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1855758 (view as bug list) Environment:
Last Closed: 2020-10-09 14:56:55 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: 1855758    
Bug Blocks:    

Description SATHEESARAN 2020-07-10 12:20:31 UTC 
Description of problem:
-----------------------
During RHHI-V deployment, auto-populate the LV cache size for the other hosts, when the value for the first host is provided.

Currently when the LV cache size of the first host is provided, the lV cache size of other 2 hosts are still retains the constant value '1'

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
cockpit-ovirt-dashboard-0.14.9

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

Steps to Reproduce:
-------------------
1. Start RHHI-V /Hyperconverged deployment from web console (cockpit)
2. On the bricks tab, enable LV cache, and populate the LV cache size
3. Go to the second and third host, and look for value of LV cache

Actual results:
---------------
LV cache size on the host2 and host3, remains as '1'

Expected results:
-----------------
Device names gets autopopulated on host2 and host3, similarly the LV cache size should also get auto-populated
Comment 4 SATHEESARAN 2020-09-07 06:35:39 UTC 
Verified with cockpit-ovirt-dashboard-0.14.11, the LV cache size is automatically populated based on the LV size of the first host