Description of problem: ----------------------- When NBDE setup is completed, the target device is created under /dev/mapper/luks_sdx. When attempting for RHHI-V deployment from web console(cockpit), and attaching the LVM cache, logic uses device name as '/dev/luks_sdc' instead of '/dev/mapper/luks_sdc' Version-Release number of selected component (if applicable): ------------------------------------------------------------- cockpit-ovirt-dashboard-0.14.8 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Start the HC deployment from cockpit 2. On the bricks tab provide the device name as '/dev/mapper/luks_sdc' 3. Enable LVM cache and provide SSD as '/dev/sdg' Actual results: --------------- Generated inventory file contains reference to '/dev/luks_sdc' Expected results: ------------------ Generated inventory file should contain '/dev/mapper/luks_sdc' --- Additional comment from SATHEESARAN on 2020-06-18 12:24:17 UTC --- The generated inventory contains: <snip> gluster_infra_cache_vars: - vgname: gluster_vg_luks_sdc cachedisk: '/dev/luks_sdc,/dev/sdg' cachelvname: cachelv_gluster_thinpool_gluster_vg_luks_sdc cachethinpoolname: gluster_thinpool_gluster_vg_luks_sdc cachelvsize: 220G cachemode: writethrough </snip> Expected is that the device should be */dev/mapper/luks_sdc* <snip> gluster_infra_cache_vars: - vgname: gluster_vg_luks_sdc cachedisk: '/dev/mapper/luks_sdc,/dev/sdg' cachelvname: cachelv_gluster_thinpool_gluster_vg_luks_sdc cachethinpoolname: gluster_thinpool_gluster_vg_luks_sdc cachelvsize: 220G cachemode: writethrough </snip> --- Additional comment from SATHEESARAN on 2020-06-18 12:26:59 UTC --- This error is also true for multipath configuration enabled, where the device name is '/dev/mapper/WWID' for example: /dev/mapper/3600304801a48610125f9a6571e612c29
Tested with cockpit-ovirt-dashboard-0.14.9.el8rhgs When attaching the LVM cache ( /dev/sdx ) with the LUKS device ( /dev/mapper/luks_sdx ), the deployment happens in the right way.
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 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.