Bug 2153623

Summary: dracut misses out a line in /etc/crypttab
Product: [Fedora] Fedora Reporter: customercare
Component: dracutAssignee: dracut-maint-list
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 36CC: dracut-maint-list, jamacku, lnykryn, pvalena
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 15:56:12 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:

Description customercare 2022-12-14 23:12:15 UTC
Version-Release number of selected component (if applicable):

dracut 057-3 

Description of problem:

SYSTEM: /etc/crypttab

luks-92b93668-3c6b-4b88-9c19-8575292c14ed UUID=92b93668-3c6b-4b88-9c19-8575292c14ed /dev/disk/by-id/usb-XXXXXXXXXXXXXXXXXXX-0:0 luks,tries=3,key...
luks-1ba1a9d5-7aef-4ccc-83fe-15b43458d9b9 UUID=1ba1a9d5-7aef-4ccc-83fe-15b43458d9b9 /dev/disk/by-id/usb-XXXXXXXXXXXXXXXXXXX-0:0 luks,tries=3,key....

one is "/", one is swap

As you can see, a keyfile in form of usb drive shall unlock the disks, both.

dracut -f produces this /etc/crypttab inside the initramfs image:

luks-92b93668-3c6b-4b88-9c19-8575292c14ed /dev/disk/by-uuid/92b93668-3c6b-4b88-9c19-8575292c14ed /dev/disk/by-id/usb-XXXXXXXXXXXXXXXXXXX-0:0 luks,tries=3,key...

"..." just some more options, not relevant.

This leads to the following situation:

The first "/" partition is correctly unlocked, but plymouth asks for the swap partition's password to unlock it, which succeeds when entered correctly.

Correctly, both partitions shall be unlocked by the same keyfile, but as no entry is in the crypttab to hint the init system to do so, it falls back to passwords. 

And it's impossible to trick dracut into overwriting the generated file with a (hopefully) working crypttab version with two entries.

Both parititons are on the same physical device. 

The same behavior of dracut can be observed, if no keyfile is used ("none" is given as the third crypttab  argument ). It looks like a general bug.

Addition Infos:

NAME                                          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda                                             8:0    0 223,6G  0 disk  
├─sda1                                          8:1    0   500M  0 part  /boot
├─sda2                                          8:2    0 223,1G  0 part  
│ └─luks-92b93668-3c6b-4b88-9c19-8575292c14ed 253:0    0 223,1G  0 crypt /
└─sda3                                          8:3    0     6M  0 part  
  └─luks-1ba1a9d5-7aef-4ccc-83fe-15b43458d9b9 253:1    0     4M  0 crypt

Comment 1 customercare 2022-12-14 23:49:28 UTC
additional info:

if i comment out the line for the "/" partition, the second for Swap is still not included in the created crypttab.

So this entry is completly ignored. In the above example, it's:

luks-1ba1a9d5-7aef-4ccc-83fe-15b43458d9b9 UUID=1ba1a9d5-7aef-4ccc-83fe-15b43458d9b9 /dev/disk/by-id/usb-XXXXXXXXXXXXXXXXXXX-0:0 luks,tries=3,key....

Except it the swap partition, it's just a normal partition on the drive , nothing special I can see.

Comment 2 customercare 2022-12-15 16:15:11 UTC
Update:

"forcing" the second partition to be in the crypttab, solves the original issue. 

change crypttab for missing partition to :

luks-1ba1a9d5-7aef-4ccc-83fe-15b43458d9b9 UUID=1ba1a9d5-7aef-4ccc-83fe-15b43458d9b9 /dev/disk/by-id/usb-XXXXXXXXXXXXXXXXXXX-0:0 force,luks,tries=3,key....

fire "dracut -f " and it works as expected.

Comment 3 Ben Cotton 2023-04-25 18:15:21 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ludek Smid 2023-05-25 15:56:12 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.