Bug 1745498

Summary: VDO with LVM thinpool needs correct entry in inventory file in cockpit based deployment.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Gobinda Das <godas>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: bipin <bshetty>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhiv-1.6CC: rhs-bugs, sasundar
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:
: 1745503 (view as bug list) Environment:
Last Closed: 2019-10-03 12:24:01 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: 1745503    
Bug Blocks:    

Description Gobinda Das 2019-08-26 08:58:23 UTC
Description of problem:
 While enabling thinp for VDO from cockpit, it specifies 100%FREE and logicalvolume section does not show actual size which causing deployment failure.
gluster_infra_thick_lvs:
        - vgname: gluster_vg_sdb
          lvname: gluster_lv_engine
          size: 1000G
        - vgname: gluster_vg_sdb
          lvname: gluster_lv_data
          size: 4000G
        - vgname: gluster_vg_sdb
          lvname: gluster_lv_vmstore
          size: 100%FREE
      gluster_infra_thinpools:
        - vgname: gluster_vg_sdb
          thinpoolname: gluster_thinpool_gluster_vg_sdb
          poolmetadatasize: 2G
      gluster_infra_lv_logicalvols:
        - vgname: gluster_vg_sdb
          thinpool: gluster_thinpool_gluster_vg_sdb
          lvname: gluster_lv_data
          lvsize: 400G
        - vgname: gluster_vg_sdb
          thinpool: gluster_thinpool_gluster_vg_sdb
          lvname: gluster_lv_vmstore
          lvsize: 400G


gluster_infra_thick_lvs should not have thip entry.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 SATHEESARAN 2019-08-26 10:05:12 UTC
The other scenario that needs to be taken here is that, 
the size of LV should be multiplied by 10, in case of VDO enabled.
Else, the size should remain the same as that given from user

Comment 3 SATHEESARAN 2019-09-05 16:31:49 UTC
The fix is now available as part of the cockpit-ovirt-dashboard-0.13.8

Comment 4 SATHEESARAN 2019-09-05 16:32:06 UTC
verified with cockpit-ovirt-dashboard-0.13.8

There are no thick LV configuration in the generated vars file, when VDO option is selected.
Also the size of LVs are 10 times the original size in input, when VDO option is selected

Comment 6 errata-xmlrpc 2019-10-03 12:24:01 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