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
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
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.