RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug was initially created as a copy of Bug #1722182

I am copying this bug because: 
It is still a bug in 8.x.


Description of problem:
It is possible to use a keydev to unlock a luks root volume at boot since https://github.com/lnykryn/systemd-rhel/pull/231 (#1619743)
However, when the device used as keydev is not present (for example an unplugged usb drive) it is not possible to provide a password as fallback.

Version-Release number of selected component (if applicable):
systemd-219-62.el7_6.6.src.rpm

How reproducible:
Always

Steps to Reproduce:
1. Configure a keydev for a luks root volume
2. Remove the device that is used as keydev
3. Reboot

Actual results:
After a very long timeout the dracut shell starts.

Expected results:
After a reasonable timeout the user is asked for a password. When entering the correct password the system boots normally.

Additional info:
Attached a patch for systemd-219-62.el7_6.6.src.rpm that allows the user to enter a password when the keydev device is not present.

PR: https://github.com/systemd-rhel/rhel-8/pull/53

fix merged to github master branch -> https://github.com/systemd-rhel/rhel-8/pull/77

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, 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/RHSA-2020:1794