dracut-102 newly starts systemd-cryptsetup@usbBoot.service on the encrypted device "usbBoot", trying to read a passphrase from /dev/tty1. Thankfully, after three failed attempts at that (if one enters three CRs...), processing continues as usual and dracut successfully employs rd.luks.name and rd.luks.key as instructed from the (grub) kernel command line. Note that the original issue names tpm unlock but the problem is the autodetection kicking in before the explicit luks instructions are used. Workaround (verified): Set rd.auto=0 in kernel parameters. Reproducible: Always
