Bug 1977611

Summary: PC is not booting with disk encryption and configured tangd/clevis with rd.neednet=1
Product: [Fedora] Fedora Reporter: Radomir Ludva <rludva>
Component: dracutAssignee: dracut-maint-list
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: dracut-maint-list, jonathan, paul.0000.black, surkum, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 20:44:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Initial error
none
Next warnings during the boot..
none
Final emergency shell.. none

Description Radomir Ludva 2021-06-30 07:35:44 UTC
Description of problem:
-----------------------
After the latest update of the Fedora34 system (2021-06-30) the PC is not booting correctly. It is only visible when you have an encrypted drive and when you are using tangd to encrypt it without typing manually the password. You need rd.neednet=1 in the kernel arguments but the network is not starting correctly with some strange message about missing init-rd-no-auto-default.conf.

Before the update, everything was working correctly.
Tested on two PC.


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
fedora-release-workstation-34-1.noarch
fedora-release-common-34-1.noarch


How reproducible:
-----------------
Not sure if it is only because of the rd.neetnet=1 but when it is removed the system is asking for a password and booting correctly.


Additional info:
----------------
I will share screenshots (photos) of the boot process..


Workaround:
-----------
- Edit the kernel arguments during the boot and remove rd.neetnet=1

Comment 1 Radomir Ludva 2021-06-30 07:40:49 UTC
Created attachment 1796137 [details]
Initial error

Comment 2 Radomir Ludva 2021-06-30 07:42:27 UTC
Created attachment 1796138 [details]
Next warnings during the boot..

Comment 3 Radomir Ludva 2021-06-30 07:43:50 UTC
Created attachment 1796139 [details]
Final emergency shell..

Comment 4 Paul Black 2021-07-06 18:47:50 UTC
This has stopped working for me as well on Fedora IoT. Removing the rd.neednet=1 did not help.

Comment 5 Radomir Ludva 2021-07-23 08:06:29 UTC
This BZ looks like a duplicate of [1]

[1] Bug 1976641 - dbus-broker-29-1 update breaks automated unlocking of encrypted volumes at boot time via clevis
    https://bugzilla.redhat.com/show_bug.cgi?id=1976641

Comment 6 Ben Cotton 2022-05-12 15:05:01 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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 '34'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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.

Comment 7 Ben Cotton 2022-06-07 20:44:39 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.