Bug 1746451

Summary: lvcache should be the same as input from user
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhiv-1.6CC: godas, rhs-bugs
Target Milestone: ---Keywords: ZStream
Target Release: RHHI-V 1.6.z Async Update   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-dashboard-0.13.8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1746452 (view as bug list) Environment:
Last Closed: 2019-10-03 12:24:16 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: 1746452    
Bug Blocks:    

Description SATHEESARAN 2019-08-28 13:41:51 UTC 
Description of problem:
------------------------
lvcache size should be the same as the one received from the user


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

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

Steps to Reproduce:
--------------------
1. Enable lvcache
2. Input the size of lvcache

Actual results:
-----------------
Generated vars file has the lvcache size much lesser than the input one

Expected results:
-----------------
lvcache in generated vars file should be the same as input one


Additional info:
Comment 1 SATHEESARAN 2019-09-05 12:23:06 UTC 
I could see that this fix is part of cockpit-ovirt-dashboard-0.13.8
LV cache size from the input is reflected in the generated vars file
Comment 2 SATHEESARAN 2019-09-05 16:26:47 UTC 
The fix is available as part of the cockpit-ovirt-dashboard-0.13.8
Comment 3 SATHEESARAN 2019-09-05 16:27:12 UTC 
based on comment1, verifying this bug
Comment 5 errata-xmlrpc 2019-10-03 12:24:16 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/RHBA-2019:2963