Description of problem: I have a LUKS-encrypted root partition protected by TPM2 with a recovery key. I updated from Fedora 35 Workstation to the Fedora 36 beta using the following commands: 1) sudo dnf system-upgrade download --releasever=36 --allowerasing --skip-broken 2) sudo dnf system-upgrade-reboot Upon reboot, grub2 allows selecting a kernel. If the Fedora 36-associated latest kernel (5.17.3-302.fc36.x86_64 on my machine) is selected, some more boot script runs before hanging. A message, "Warning: dracut-initqueue: starting timeout scripts" with some associated text, repeats rapidly until I'm dropped at an emergency shell. After booting into a live USB, mounting and chrooting into my local install, I regenerated the grub config; however, could not run dracut -f as it gave the error: "dracut: module "crypt" depends on "tpm2-tss", which can't be installed." I then found I was able to boot into the older kernel using grub, later finding this report: https://bugzilla.redhat.com/show_bug.cgi?id=2058833 As my setup matched the one in the issue (namely "tpm2-device=auto" appearing in /etc/crypttab), I installed tpm2-tools via dnf, then ran: 1) sudo dracut '' 5.17.3-302.fc36.x86_64 -f 2) sudo grub2-mkconfig -o /etc/grub2-efi.cfg and the issue resolved. Version-Release number of selected component (if applicable): kernels: kernel-5.16.20-200.fc35.x86_64 -> kernel-5.17.3-302.fc36.x86_64 dracut: dracut-055-6.fc35 (on F35), dracut 056-1.fc36 (on F36) How reproducible: Occurred every reboot until I found a fix. Steps to Reproduce: 1. Have a TPM-protected, LUKS root partition. 2. sudo dnf system-upgrade download --releasever=36 --allowerasing --skip-broken 3. sudo dnf system-upgrade-reboot Actual results: Broken boot environment as described above. Expected results: Machine boots into Fedora 36. Additional info:
Thanks for the report. Do you think adding the following to spec would help? I can send test build. ``` Recommends: (tpm2-tools if tpm2-tss) ```
https://src.fedoraproject.org/rpms/dracut/pull-request/24
The change we're proposing is a workaround as this probably should not happen during package upgrade (tpm2-tss was sufficient for previous `dracut` run).
Hello Krystopher, thanks for the bug report. Can you verify you had `tpm2-tss` installed, but `tpm2-tools` was really needed as well?
Why is this reassigned to tpm2-tss?
FEDORA-2022-0fb75a6d1c has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0fb75a6d1c
FEDORA-2022-0fb75a6d1c has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-0fb75a6d1c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0fb75a6d1c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-0fb75a6d1c has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
(In reply to Peter Robinson from comment #5) > Why is this reassigned to tpm2-tss? As this is a workaround, the fix would be ideally in fixing the upgrade path, as tpm2-tss broke compatibility. I've referenced the bug, but did not intend to close this... sorry See my Comment 3 for details.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days