Antonio Álvarez Feijoo

> > Writing `uninitialized\n` to it, according to https://systemd.io/BUILDING_IMAGES/ > > I think the first boot semantics makes no sense in initrd, hence `etc/machine-id` should be _empty_ (https://www.freedesktop.org/software/systemd/man/machine-id.html#First%20Boot%20Semantics). Right, thanks...

This is wrong, `dracut-initramfs-restore` does not need the `DRACUT_SYSTEMD` env var, it does not run within the initramfs, but after switching to root, so no calls to any function defined...

> Indeed. > > However, the bug remains. During `shutdown.sh` (dracut `shutdown` module and any `shutdown` hook) the `DRACUT_SYSTEMD=1` environment variable is missing. Right, now I see the problem. >...

You can try this patch and give some feedback. If it works, update your PR with it. ```patch diff --git a/modules.d/99shutdown/shutdown.sh b/modules.d/99shutdown/shutdown.sh index 73550ba9..6b1e526b 100755 --- a/modules.d/99shutdown/shutdown.sh +++ b/modules.d/99shutdown/shutdown.sh @@...

> > > Seems like this is actually a systemd bug? systemd's system-shutdown > > > https://github.com/systemd/systemd/blob/main/src/shutdown/shutdown.c > > > should set the `DRACUT_SYSTEMD=1` environment variable because that runs `/run/initramfs/shutdown`?...

That's ok, but before dropping the network-legacy module, I'd first make sure that any of the other network modules support all of the command line parameters that the legacy module...

The initial review is here: #1876 On paper the features that NM lacks are minor. We cannot test every possible setup, but I think @tblume is having some issues with...

/packit build

#1816 would be useful right now... :)

I found this useful tool which allows to locally test these kind of github actions: https://github.com/nektos/act Although the docker tags look good, it throws the same error: ``` # act...