+++ This bug was initially created as a clone of Bug #1550988 +++ Description of problem: ------------------------ gdeploy execution should halt when the task of enabling lvmcache fails. In gdeploy terms - 'ignore_lv_errors' should be set to 'no' under lvmcache enabling section in generated config 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. Initiate RHHI deployment using cockpit 2. Enable LVMcache 3. Observe the generated gdeploy config file Actual results: --------------- 'ignore_lv_errors' is set to 'yes' Expected results: ----------------- 'ignore_lv_errors' should be set to 'no' Additional info: ---------------- actual snip in gdeploy config file: [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 Expected: [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=no
patches are included in 4.2.2 build happening today
Created attachment 1422995 [details] screenshot of ignore lv error
Tested with the following-: 1. RedHat-release-virtualization-host-4.2-2.1.el7.x86_64 2. Cockpit-ovirt-dashboard-0.11.20-1 3. gdeploy-2.0.2-19.el7rhgs.noarch Following were the steps performed to test:- 1.Log in to the cockpit UI and configure all the parameters required for the gluster deployment. 2. Check the gdeploy config file and there is the presence of parameter of 'ignore_lv_errors=no'. 3.The gdeploy execution halts whenever there is an lvmcache error. Created an attachment 1422995 [details].
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.