Bug 1855756 - auto-populate LV cache size for other hosts during deployment
Summary: auto-populate LV cache size for other hosts during deployment
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: RHHI-V 1.8.z Batch Update 1
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1855758
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-10 12:20 UTC by SATHEESARAN
Modified: 2020-10-09 14:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1855758 (view as bug list)
Environment:
Last Closed: 2020-10-09 14:56:55 UTC
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.