Description of problem: ------------------------- Few of the params in lvcache section are not required and will be auto-computed Following variables are not required: cachethinpoolname: gluster_thinpool_gluster_vg_sdd cachemetalvsize: 2G Version-Release number of selected component (if applicable): --------------------------------------------------------------- RHHI-V 1.6 cockpit-ovirt-dashboard-0.13.5 How reproducible: ----------------- NA Steps to Reproduce: -------------------- 1. Enable lv cache Actual results: --------------- 1. cache lv meta size is computed 2. lv cache meta name is computed Expected results: ------------------ When the above said options are not mentioned, lv cache meta is automatically computed by LV which is more safer Additional info:
(In reply to Gobinda Das from comment #0) > Description of problem: > ------------------------- > Few of the params in lvcache section are not required and will be > auto-computed > > Following variables are not required: > cachethinpoolname: gluster_thinpool_gluster_vg_sdd > cachemetalvsize: 2G Incorrect description. It was not the **cachethinpoolname** but the **cachemetalvname**
Tested with cockpit-ovirt-dashboard-0.13.6 All the optional params for lvcache are removed, leaving LVM to compute it by default. LV cache related params in the generated vars file looks like: <snip> gluster_infra_cache_vars: - vgname: gluster_vg_sdb cachedisk: '/dev/sdb,/dev/sdc' cachelvname: cachelv_gluster_thinpool_gluster_vg_sdb cachethinpoolname: gluster_thinpool_gluster_vg_sdb cachelvsize: 225G cachemode: writeback </snip>
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.