Description of problem: ------------------------ The ansible playbook that helps with NBDE setup, adds the disk name ( /dev/sdb ) with entry in /etc/crypttab. The disks may change during the boot and this naming convention is not persistent. ( not guaranteed to be persistent ). /etc/crypttab entries should have UUID replaced with disk names Version-Release number of selected component (if applicable): ------------------------------------------------------------- gluster-ansible-infra-1.0.4-5.el8rhgs.noarch.rpm How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Complete the NBDE setup with ansible playbook Actual results: ---------------- /etc/crypttab contains the entry with non-persistent disk names of LUKS device Expected results: ----------------- /etc/crypttab should contain entry with UUID of the LUKS device Additional info: ---------------- The following command fetches the UUID of the LUKS device: # cryptsetup luksUUID <dev> Example: [root@ ~]# cryptsetup luksUUID /dev/vdb 432998f5-f94a-4c74-9254-63238af26f71 /etc/fstab entry for the same: [root@ ~]# cat /etc/crypttab luks-1a44ea7b-1937-4e94-bf03-1bbe286cf7cc UUID=1a44ea7b-1937-4e94-bf03-1bbe286cf7cc none discard luks-vdb UUID=432998f5-f94a-4c74-9254-63238af26f71
Tested with gluster-ansible-infra-1.0.4-6 After encrypting the additional disks, the crypttab entries are created with LUKS UUID of the device
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