Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1628258 - dracut-network is holding boot until having network link
Summary: dracut-network is holding boot until having network link
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: clevis
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sergio Correia
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: IoT
TreeView+ depends on / blocked
 
Reported: 2018-09-12 15:08 UTC by Nicolas Chauvet (kwizart)
Modified: 2020-09-25 16:40 UTC (History)
12 users (show)

Fixed In Version: clevis-14-1.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-07 17:13:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/latchset clevis issues 54 0 None None None 2020-08-28 18:28:07 UTC

Description Nicolas Chauvet (kwizart) 2018-09-12 15:08:04 UTC
Description of problem:
On my fedora-28 x86_64 workstation, I'm experiencing a random failure to "switch-root" as appropriate. After the luks password is given, the boot hold and timeout.
This seems related to having a network link or not.

Version-Release number of selected component (if applicable):
dracut-048-14.git20180726.fc28
dracut-network-048-14.git20180726.fc28
dracut-config-rescue-048-14.git20180726.fc28

How reproducible:
randomly (seems related to no ethernet network link)


Steps to Reproduce:
1. Remove the ethernet wire
2. boot a fedora workstation with luks
3. 

Actual results:
Boot is sometime hold and fall into the rescue shell

Expected results:
It should boot

Additional info:
I'm not using any remote network resources (no disk in fstab or else), so I don't know what's holding the boot.
At least it seems that the network-online timeout is higher than the switch root timeout..

Also note that I cannot remove the dracut-network module here as It's a dependency of kexec-tools which is needed for various gnome workstation components. This might be a separate issue.

Comment 1 Nicolas Chauvet (kwizart) 2018-11-05 16:15:31 UTC
Seems like I have clevis installed on my laptop (but not configured).
Does clevis assume the device must be network connected or is it possible to assume keyboard interaction as a fallback when there is no network ?

Comment 2 Javier Martinez Canillas 2018-11-27 09:36:23 UTC
(In reply to Nicolas Chauvet (kwizart) from comment #1)
> Seems like I have clevis installed on my laptop (but not configured).
> Does clevis assume the device must be network connected or is it possible to
> assume keyboard interaction as a fallback when there is no network ?

When the clevis dracut module is installed, it adds a rd.neednet=1 to the cmdline even when it's not used. I wonder if this is the same than bug 1612131 and upstream dracut bug https://github.com/dracutdevs/dracut/issues/407.

Could you please do the following to test if that's the case, remove the clevis-dracut package, re-generate your initramfs and add rd.neednet=1 to your kernel command line parameters.

And then check if dracut hangs on boot and drops into the rescue shell.

Comment 3 Peter Robinson 2018-11-28 13:33:14 UTC
So we've worked around this in the IoT edition with the following:

/etc/dracut.conf.d/iot-clevis.conf 
omit_dracutmodules+="network ifcfg"

Comment 4 Daniel Helgenberger 2018-12-02 10:04:11 UTC
(In reply to Javier Martinez Canillas from comment #2)
> When the clevis dracut module is installed, it adds a rd.neednet=1 to the
> cmdline even when it's not used. I wonder if this is the same than bug
> 1612131 and upstream dracut bug
> https://github.com/dracutdevs/dracut/issues/407.

It seems the kernel default is rd.neednet=1. This holds boot until there is a network link. I explicitly need to set it to 0 to continue boot.

Comment 5 Ben Cotton 2019-05-02 19:47:07 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Peter Robinson 2019-05-03 10:42:45 UTC
Still not suitably resolved

Comment 7 Richard W.M. Jones 2019-10-04 11:47:04 UTC
The workaround added for this bug seems to break clevis-dracut entirely.
See https://bugzilla.redhat.com/show_bug.cgi?id=1687753#c2

Comment 8 Peter Robinson 2019-10-04 13:22:49 UTC
(In reply to Richard W.M. Jones from comment #7)
> The workaround added for this bug seems to break clevis-dracut entirely.
> See https://bugzilla.redhat.com/show_bug.cgi?id=1687753#c2

In what use case? For Tang unlock, TPM2 or some other one. There is work on a proper fix in progress.

Comment 9 Richard W.M. Jones 2019-10-04 14:52:21 UTC
For Tang.

Comment 10 Paul Kronenwetter 2019-10-22 13:25:31 UTC
I was able to work around this by re-adding "rd.neednet=1" to GRUB_CMDLINE_LINUX in /etc/default/grub, creating /etc/dracut.conf.d/clevis.conf with the contents of 'add_dracutmodules+="network ifcfg"' then re-generating initrd and /boot/grub2/grub.cfg.

I find that it takes a long time to boot compared to a similarly configured CentOS 7 system.

Comment 11 Felix Schwarz 2019-11-06 16:27:15 UTC
(In reply to Peter Robinson from comment #8)
> There is work on a proper fix in progress.

Is there some public issue where I can track that work?
I think I'm affected by this bug and I'd like to try out potential fixes as soon as possible.

Comment 12 Fedora Update System 2020-08-31 12:39:40 UTC
FEDORA-2020-b35219394f has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b35219394f

Comment 13 Fedora Update System 2020-08-31 13:18:29 UTC
FEDORA-2020-d42f4e90f9 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d42f4e90f9

Comment 14 Fedora Update System 2020-08-31 15:55:48 UTC
FEDORA-2020-d42f4e90f9 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-d42f4e90f9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d42f4e90f9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 15 Fedora Update System 2020-08-31 18:58:01 UTC
FEDORA-2020-b35219394f has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-b35219394f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b35219394f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 16 Fedora Update System 2020-09-07 17:13:43 UTC
FEDORA-2020-d42f4e90f9 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2020-09-25 16:40:12 UTC
FEDORA-2020-b35219394f has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.