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:
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
The fix is now available as part of the cockpit-ovirt-dashboard-0.13.8
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
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