Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem: Boot hangs when trying to unlock multiple LUKS devices Version-Release number of selected component (if applicable): systemd-239-13.el8.x86_64 dracut-049-10.git20190115.el8.x86_64 clevis-11-2.el8.x86_64 clevis-systemd-11-2.el8.x86_64 clevis-dracut-11-2.el8.x86_64 clevis-luks-11-2.el8.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Install RHEL 8.0 w/ multiple LUKS1 devices 2. Configure the LUKS devices to be decrypted with tang server 3. Reboot Actual results: Boot hangs without decrypting the non-root partitions. The following message is observed: "A start job is running for <device> (2min 11s / no limit)" Expected results: All devices should decrypt without user intervention. Additional info: Partition layout used: $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 1024M 0 rom vda 252:0 0 20G 0 disk ├─vda1 252:1 0 1G 0 part /boot └─vda2 252:2 0 19G 0 part ├─rhel-root 253:0 0 8G 0 lvm │ └─luks-d94bb88d-2de3-4809-a188-01eed1ebb94b 253:4 0 8G 0 crypt / ├─rhel-swap 253:1 0 1G 0 lvm │ └─luks-db8c178b-f893-4144-8c13-2c5833bbda1e 253:3 0 1022M 0 crypt [SWAP] ├─rhel-usr 253:2 0 2G 0 lvm │ └─luks-1f3277c5-a396-47e2-9e1f-29c976b2f245 253:5 0 2G 0 crypt /usr ├─rhel-var 253:6 0 2G 0 lvm │ └─luks-c695d0af-b6a0-4e93-941f-53c0f36c865d 253:14 0 2G 0 crypt /var ├─rhel-tmp 253:7 0 1G 0 lvm │ └─luks-ea73ddab-317b-4001-b406-f4a3113485eb 253:13 0 1022M 0 crypt /tmp ├─rhel-var_log 253:8 0 1G 0 lvm │ └─luks-e1f271fd-e1ae-434f-838b-d278715a02a4 253:17 0 1022M 0 crypt /var/log ├─rhel-var_log_audit 253:9 0 1G 0 lvm │ └─luks-3f761f91-cea9-4dba-a8ce-87a934d6f0ad 253:16 0 1022M 0 crypt /var/log/audit ├─rhel-home 253:10 0 1G 0 lvm │ └─luks-595607f0-7e66-47a4-8ce7-d7637fe159ce 253:12 0 1022M 0 crypt /home └─rhel-opt 253:11 0 2G 0 lvm └─luks-c85ec99c-2ba2-4e7a-bc76-7982fdfea674 253:15 0 2G 0 crypt /opt