Description of problem: ----------------------- Technically, when the user enables 'blacklist gluster devices' option, the devices should be of format /dev/sdx. But there are chances, users could provide insane values or provide LUKS devices ( /dev/mapper/luks_sdb ) those were created via executing ansible playbook In this case, when 'blacklist gluster devices' is enabled and user provides device values as /dev/mapper/x, do not add those devices under 'blacklist_mpath_devices' in the generated inventory file Version-Release number of selected component (if applicable): -------------------------------------------------------------- cockpit-ovirt-dashboard-0.14.3 How reproducible: ----------------- Always Steps to Reproduce: -------------------- 1. Start RHHI-V/HC deployment from web console 2. On the 'bricks' tab, enable the option 'Blacklist Gluster Devices', which is selected by default 3. Provide disk values as /dev/mapper/luks_sdb Actual results: ---------------- Generated inventory file contains luks_sdb Expected results: ----------------- Generated inventory file should not contain luks_sdb Additional info:
Tested with cockpit-ovirt-dashboard-0.14.5 When the device name is provided as /dev/mapper/luks_sdb, and that device is not added to the 'blacklist_mpath_devices' in the generated inventory file. There is one known issue in this context. When there are less than 3 bricks devices are to be blacklisted, an empty '' is added to the list of devices to blacklisted, but just gets skipped and doesn't impact the deployment. So this issue is ignored
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 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.