Bug 27178

Summary:	Dracut does not recognize rd.luks.key correctly
Product:	Mageia	Reporter:	Marc Krämer <mageia>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	NEW ---	QA Contact:	Base system maintainers <basesystem>
Severity:	normal
Priority:	Normal	CC:	ouaurelien
Version:	8
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	dracut-046-11.mga7.src.rpm	CVE:
Status comment:

Description Marc Krämer 2020-08-22 12:39:45 CEST

I try to setup an laptop with a key file on usb stick.
I've added the kernel cmd-line 
rd.luks.key=/crypt

On restart dracut searches for the image on all devices but NOT on the attached USB stick.
I can see messages about probing for the file "/crypt" on different devices, fails for the first time, then USB devices are detected and it executes again, but on all probed devices USB stick (partiions) is missing.

extending
rd.luks.key=/crypt:UUID=xxxxx

does not solve the issue, there is no probe output anymore, but I assume it does not find the device via UUID because the usb detection is too late.

Comment 1 Marc Krämer 2020-08-22 13:10:16 CEST

some additional info:
1. the filesystem on external (usb-stick) has to be the same as the root filesystem, since dracut only includes the kernel drivers for this filesystem
2. specifying UUID fails everytime, even if the UUID is correct (since I don't get output, I don't know if the expect the UUID with capitals or like /dev/by-uuid lowercase)
3. removing UUID succeeds, but due to the late detection of USB takes some time and does not look very relyable

Comment 2 Aurelien Oudelet 2020-08-22 17:12:02 CEST

Hi, thanks reporting this.

Assigning globally to all packagers as there is not currently a dedicated maintainer.

CC: Basesystem Team.

Have you also test this behaviour on Cauldron?

Assignee: bugsquad => pkg-bugs
CC: (none) => ouaurelien
QA Contact: (none) => basesystem

Comment 3 Aurelien Oudelet 2021-07-06 13:14:48 CEST

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Marc Krämer 2021-07-06 13:24:37 CEST

Version: 7 => 8