+++ This bug was initially created as a clone of Bug #1552524 +++ Description of problem: ----------------------- lvmcache size is missing units in the generated gdeploy configuration file Version-Release number of selected component (if applicable): ------------------------------------------------------------- cockpit-ovirt-dashboard-0.11.12-0.1.el7ev.noarch How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Start the RHHI installation with cockpit 2. Enable lvmcache during installation 3. Investigate the generated gdeploy configuration file Actual results: --------------- lvmcache section has the lvmcache size without units mentioned Expected results: ----------------- lvmcache size should be with the units of GB Additional info: ---------------- <actual_content> [lv5] action=setup-cache ssd=sdc vgname=gluster_vg_sdb poolname=gluster_thinpool_sdb cache_lv=lvcache cache_lvsize=220 cachemode=writethrough ignore_lv_errors=yes </actual_content> <expected_content> action=setup-cache ssd=sdc vgname=gluster_vg_sdb poolname=gluster_thinpool_sdb cache_lv=lvcache cache_lvsize=220GB cachemode=writethrough ignore_lv_errors=yes </expected_content>
Issue fixed in 88778 id
This Bug is tested with the following versions ------------------------------------------------ * cockpit-ovirt-dashboard-0.11.21-1.el7ev.noarch * redhat-release-virtualization-host-4.2-2.1.el7.x86_64 Steps to reproduce ---------------------------------------------- 1. Start with Installation of RHHI 2.0 2. Specify the storage details by enabling the LVM cache 3. Check the gdeploy config file generated. The Expected Results match with the actual result ------------------------------------------------- [lv2:10.70.36.83] action=create poolname=gluster_thinpool_sdc ignore_lv_errors=no vgname=gluster_vg_sdc lvtype=thinpool size=11280GB poolmetadatasize=16GB
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 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.