Bug 33266

Summary:	dracut : module has transitive dependency on systemd
Product:	Mageia	Reporter:	Eric Petit <surfzoid>
Component:	RPM Packages	Assignee:	Kernel and Drivers maintainers <kernel>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins, surfzoid
Version:	9
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	dracut-057.4.1.mga9	CVE:
Status comment:
Attachments:	dracut.conf dracut.conf50 dracut.conf51 dracut.conf98

Description Eric Petit 2024-06-04 08:53:28 CEST

Hi
today update install "microcode", it run dracut whose give the following errors:
55/55: microcode             #############################################
dracut: dracut module 'systemd-initrd' depends on 'systemd', which can't be installed
dracut: dracut module 'ifcfg' depends on 'network', which can't be installed
dracut: dracut module 'systemd-initrd' depends on 'systemd', which can't be installed
dracut: dracut module 'dracut-systemd' depends on 'systemd-initrd', which can't be installed
dracut: dracut module 'ifcfg' depends on 'network', which can't be installed

This thread suggest workaround https://github.com/dracutdevs/dracut/issues/1756 :
omit_dracutmodules+=" systemd systemd-networkd "
add_dracutmodules+=" network-legacy "
to dracut.conf, but i don't test that because i dom't want to break my boot system.

lsinitrd -m
Image: /boot/initrd-6.6.28-desktop-1.mga9.img: 15M
========================================================================
Early CPIO image
========================================================================
drwxr-xr-x   3 root     root            0 Jun  4 08:34 .
-rw-r--r--   1 root     root            2 Jun  4 08:34 early_cpio
drwxr-xr-x   3 root     root            0 Jun  4 08:34 kernel
drwxr-xr-x   3 root     root            0 Jun  4 08:34 kernel/x86
drwxr-xr-x   2 root     root            0 Jun  4 08:34 kernel/x86/microcode
-rw-r--r--   1 root     root        97280 Jun  4 08:34 kernel/x86/microcode/GenuineIntel.bin
========================================================================
Version: dracut-4400fd7

dracut modules:
i18n
drm
plymouth
kernel-modules
kernel-modules-extra
resume
rootfs-block
terminfo
udev-rules
usrmount
base
fs-lib
shutdown
========================================================================

Comment 1 Eric Petit 2024-06-04 08:56:36 CEST

Created attachment 14557 [details]
dracut.conf

CC: (none) => surfzoid

Comment 2 Eric Petit 2024-06-04 08:57:48 CEST

Created attachment 14558 [details]
dracut.conf50

Comment 3 Eric Petit 2024-06-04 08:58:08 CEST

Created attachment 14559 [details]
dracut.conf51

Comment 4 Eric Petit 2024-06-04 08:58:30 CEST

Created attachment 14560 [details]
dracut.conf98

Comment 5 Lewis Smith 2024-06-12 21:52:56 CEST

Thank you for this full report. The dracut/issues link you give certainly looks relevant; but one wonders why you are the only person to report this failure.

Assigning to kernel.

Assignee: bugsquad => kernel

Comment 6 Eric Petit 2024-06-12 22:56:49 CEST

yes, perhaps i'm alone to use command line and read.
I'm not sure, but this bug was also on mga8, since an long time, but no error at boot time.

Comment 7 Dave Hodgins 2024-06-13 03:55:03 CEST

This has been reported before, though I won't search for it right now.

The messages are not error messages. They are information messages.

The systemd module/program can not be included as it's intentionally listed
in /etc/dracut.conf.d/50-mageia.conf in the omitmodules setting, in order
to make it easier to change what is done at boot time. and so the initrd
doesn't have to get rebuilt every time there is a systemd update

If you remove systemd from the setting in that configuration file, you will
have to pay attention to ensure you run dracut -f when ever there is a
systemd update. I haven't tried it, but I think it also means that the
initrd will have to be updated if you change what services and/or sockets
are to be started at boot and include everything else needed by those
services in the initrd.

Other messages are due to the systemd module being excluded, or to let you
know that other things that could have been included, are not presently
installed in your system, so they will not be included in the initrd.

To get rid of a "not found" message, install the package with that program,
but be careful. Installing some things can cause other things to break.
For example, installing biosdevname will change the network interface name,
so if you install it, the names of the files and devices in config files will
have to be changed too.

Status: NEW => RESOLVED
CC: (none) => davidwhodgins
Resolution: (none) => INVALID

Comment 8 Eric Petit 2024-06-13 06:28:42 CEST

Thank you dave for explanations.
I imagine that it is a team choice.