[Bug 2084639] Re: Dracut PXE/NFS boot hangs on starting network on Ubuntu 22.04

[Walid Omari]

Dear Benjamin,

I did not have much time today to test what you requested. I will do and get back to you.
However, I think we have 2 separate issues now:
- dracut with systemd module failing to boot on ubuntu 24.04, can be overcome by omitting the dracut systemd module and the system will work fine.
- dracut with ubuntu 22.04 failing whenever systemd-netword is enabled (systemd-network-generator.service and systemd-networkd-wait-online.service specifically) and disabling these services will leave the network unmanaged and the legacy naming (eth0..) is used which I believe will be problematic in case of a network boot with multiple network interfaces available on the system.

I believe the later is more critical (at least for me) as it is
preventing proper function of the system.

I have now tested both dracut versions 051 (available on the repo) and
060 (built from scratch) on ubuntu 22.04 and both resulted in the same
outcome.

Let me know what you think.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dracut in Ubuntu.
Matching subscriptions: dracut
https://bugs.launchpad.net/bugs/2084639

Title:
  Dracut PXE/NFS boot hangs on starting network on Ubuntu 22.04

Status in dracut package in Ubuntu:
  New

Bug description:
  Describe the bug
  When trying to setup NFS boot for an Ubuntu 22.04 image that is created with debootstrap, generating an initrd with dracut makes the boot hang after root pivot and init phase at "Starting wait for network to be configured...".
  Disabling/masking systemd-network-generator.service and systemd-networkd-wait-online.service as well as omitting systemd module when building the initrd image allows the system to boot but then the network is left unmanaged and the interfaces that were renamed before init from eth0 to enp0s3 (for example) is then reverted to eth0 when the system is booted and running networkctl command shows all interfaces as unmanaged
  With initramfs-tools generate initrd image, the system boots normally and the interfaces are renamed properly from "eth0" to "enp0s3" and are managed by systemd as expected.

  Distribution used
  ubuntu 22.04 LTS

  Dracut version
  tested both version 051 (available in apt repos) and 058 (built from source)

  Init system
  systemd

  To Reproduce

  Setup PXE server (dnsmasq), grub...
  Create an ubuntu 22.04 image with debootstrap, chroot into the created image, install kernel (currently using 5.15.0-25-generic) and other packages you may need.
  install dracut and dracut-network packages and build an initrd image.
  export the image with nfs-kernel-server and boot a VM/machine with it.
  Expected behavior
  I expect the system to boot properly like when using an initramfs-tools generated image.

  Additional context
  I understand dracut is not usually used on Debian/ubuntu, but the reason I want to use dracut is its modularity and I find it to be less complicated than initramfs tools and specifically I want to do an overlay with the NFS exported image which is just a rootovl kernel parameter in dracut rather than a whole custom script with initramfs-tools that I was not able to make it work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2084639/+subscriptions