Bug 1812326

Summary: LUKS device UUID should be added to entry in /etc/crypttab
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Gobinda Das <godas>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhiv-1.8CC: rhs-bugs
Target Milestone: ---   
Target Release: RHHI-V 1.8   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gluster-ansible-infra-1.0.4-6.el8rhgs Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1812327 (view as bug list) Environment:
Last Closed: 2020-08-04 14:51:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1812327    
Bug Blocks: 1779977    

Description SATHEESARAN 2020-03-11 02:07:44 UTC 
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
Comment 2 SATHEESARAN 2020-03-21 10:01:50 UTC 
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
Comment 4 errata-xmlrpc 2020-08-04 14:51:37 UTC 
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