Package: initramfs-tools-core Version: 0.137 Severity: normal Tags: patch configure_networking() will do a `udevadm settle` before trying to configure an interface. However it is possible for a NIC to appear after the event queue has settled. This is pretty reproducible with a USB NIC I have. There doesn't appear to be a good way to wait for all devices that were connected at boot time to become available - `udevadm settle` is just the closest thing we have.
However, in the case that the user has told us which interface they expect to be used in the initramfs, we can just wait for it specifically. As a bonus, this should shave off some time on systems where the NIC is available before the udev event queue has emptied. I've a patch to do this, which I'll submit as an MR in salsa. Note: This should help out with the following issue in clevis, which provides a mechanism for unlocking a LUKS root device from the initramfs by communicating with a tang server: https://github.com/latchset/clevis/issues/145 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages initramfs-tools-core depends on: ii coreutils 8.32-3 ii cpio 2.13+dfsg-3 ii e2fsprogs 1.45.6-1 ii klibc-utils 2.0.7-1 ii kmod 27+20200310-2 ii logsave 1.45.6-1 ii udev 245.6-3 Versions of packages initramfs-tools-core recommends: ii busybox 1:1.30.1-5 ii pigz 2.4-1+b1 Versions of packages initramfs-tools-core suggests: ii bash-completion 1:2.10-1 -- Configuration Files: /etc/initramfs-tools/initramfs.conf changed [not included] -- no debconf information
