Dracut expects NetworkManager's D-Bus policy file to be installed in /usr/share/dbus-1/system.d. However, Gentoo's NetworkManager package installs the file in /etc/dbus-1/system.d instead. This results in the following error when building the initrd: dracut: *** Including module: network-manager *** dracut-install: ERROR: installing '/usr/share/dbus-1/system.d/org.freedesktop.NetworkManager.conf' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.0t7igV/initramfs /usr/share/dbus-1/system.d/org.freedesktop.NetworkManager.conf Building the initrd succeeds anyway, but network does not become available during boot as the policy file cannot be found and NetworkManager cannot start up. This breaks features like remote unlocking via crypt-ssh that rely on network being available during initrd time. I have filed https://bugs.gentoo.org/796467 for tracking the unexpected location of the policy file, as I'm not sure where this should be fixed in the end (probably it would be a good idea if Dracut were a bit more robust and would also take user configuration in /etc into account either way). Reproducible: Always Steps to Reproduce: 1. Configure Dracut to include the network-manager module (direct or transitively e.g. via the crypt-ssh module) 2. Build initrd Actual Results: Error messages during build (non-fatal for some reason): dracut: *** Including module: network-manager *** dracut-install: ERROR: installing '/usr/share/dbus-1/system.d/org.freedesktop.NetworkManager.conf' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.0t7igV/initramfs /usr/share/dbus-1/system.d/org.freedesktop.NetworkManager.conf As a result, no network on boot during the initrd phase. Expected Results: No warnings/errors related to the network-manager module. Network is up and running during initrd, before the password prompt so features like crypt-ssh work. I have manually hacked /usr/lib/dracut/modules.d/35network-manager/module-setup.sh to use the "correct" path into /etc, and can confirm that with that change, everything works as expected. Bug https://bugs.gentoo.org/796467 filed to track unexpected position of the policy file.
Adding upstream issue.
should be fixed in networkmanager-1.32.10 via https://bugs.gentoo.org/show_bug.cgi?id=796467
