[Bug 2049221] Re: LUKS2 volumes are not unlocked without hostonly=yes

[Benjamin Drung]

I tested following

1. In a VM install Ubuntu 24.10 with LVM with encryption
2. Install dracut afterwards: sudo apt install dracut
3. Add rd.shell to the boot arguments
4. Reboot

It booted successfully. This was using dracut 102-3ubuntu2.

```
$ cat /etc/crypttab 
dm_crypt-0 UUID=b5422ba8-b534-41b0-8e91-ee502b5f0c4d none luks
$ cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-6.8.0-31-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
$ systemd-analyze 
Startup finished in 732ms (kernel) + 15.905s (initrd) + 4min 32.746s (userspace) = 4min 49.385s 
graphical.target reached after 4min 32.709s in userspace.
```

I assume that this setup is equivalent to yours. So I am marking this
bug as fixed. Please reopen in case you still experience this bug.

** Changed in: dracut (Ubuntu)
       Status: New => Fix Released

** Changed in: dracut (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dracut in Ubuntu.
Matching subscriptions: dracut
https://bugs.launchpad.net/bugs/2049221

Title:
  LUKS2 volumes are not unlocked without hostonly=yes

Status in dracut package in Ubuntu:
  Fix Released

Bug description:
  My system uses classic full disk encryption, my crypttab is ignored
  unless hostonly=yes is set, causing the system to wait for my
  encrypted / forever. Not sure how luks auto discovery is supposed to
  work here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2049221/+subscriptions