Description of problem: ------------------------ Blacklisting functionality available as part of RHHI-V deployment blacklists the devices. It doesn't really makes sense to blacklist md devices or luks devices create using ansible playbook. so blacklisting module should take care of the situation, when the device is either md device or luks device, then blacklisting shouldn't be done on those devices Version-Release number of selected component (if applicable): -------------------------------------------------------------- gluster-ansible-infra-1.0.4-7 How reproducible: ------------------ Always Steps to Reproduce: -------------------- 1. Start the deployment with disk devices as /dev/md127 or /dev/mapper/luks_sdb Actual results: ---------------- Deployment fails as 'multipath -a /dev/mapper/luks_sdb' returns no value (WWID) and also deployment fails as 'multipath -a /dev/md127' returns no value(WWID) Expected results: ------------------ blacklist module should not look to blacklist 'md' devices or 'luks' device created using playbook Additional info:
Verified with gluster-ansible-infra-1.0.4-8.el8rhgs 1. Provided the disks as /dev/md0 and LUKS device /dev/sdb 2. The task that does - 'multipath -a' ignores error.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (RHHI for Virtualization 1.8 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:3314