Bug 31680

Summary: dracut after microcode has trouble with systemd
Product: Mageia Reporter: w unruh <unruh>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: davidwhodgins
Version: 8   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: ? CVE:
Status comment:

Description w unruh 2023-03-15 21:36:57 CET
Description of problem:
I jus updated my Mageia 8 syste, and just after the microcode got loaded I got a bunch of dracut error messages regarding systemd 

    1/13: microcode             ###############################################################################
dracut: systemd-initrd needs systemd in the initramfs
dracut: systemd-networkd needs systemd in the initramfs
dracut: dracut module 'rngd' depends on 'systemd', which can't be installed
dracut: dracut module 'ifcfg' depends on 'network', which can't be installed
dracut: dracut-systemd needs systemd-initrd in the initramfs
dracut: dracut-squash only supports systemd bases initramfs
dracut: dracut module 'rngd' depends on 'systemd', which can't be installed
dracut: dracut module 'ifcfg' depends on 'network', which can't be installed
dracut: dracut-squash only supports systemd bases initramfs



Version-Release number of selected component (if applicable):

microcode-0.20230214-1.mga8.nonfree
dracut-051-4.mga8

How reproducible: No idea


Steps to Reproduce:
1.urpmi --auto-update
Comment 1 Dave Hodgins 2023-03-15 22:30:40 CET
They are normal messages in dracut execution. Which messages are shown depends
on what packages have been installed and options chosen in /etc/dracut.conf
or in .conf files in /etc/dracut.conf.d/

On my system after running "dracut -f>dracut.log.txt 2>&1" I get
# grep 'dracut ' dracut.log.txt 
dracut: Executing: /usr/bin/dracut -f
dracut: dracut module 'rngd' depends on 'systemd', which can't be installed
dracut: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!
dracut: dracut module 'ifcfg' depends on 'network', which can't be installed
dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found!
dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found!
dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found!
dracut: dracut module 'rngd' depends on 'systemd', which can't be installed
dracut: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!
dracut: dracut module 'ifcfg' depends on 'network', which can't be installed
dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found!
dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found!

They are information messages, not error messages. For example, the systemd
dracut module is only used if systemd, including the various service files,
sockets, etc., will all be pre-loaded from the initrd rather then the normal
method of only loading what's needed from the initrd and the rest from /etc
and /lib. Same with the network related messages.

For most of the other messages it's because the system I'm using does not have
raid or iscsi packages installed.

Anything the causes dracut to be called to regenerate the initrd or generate
a new one will have the same error messages, including kernel updates,
microcode, and dkms packages.

Closing as invalid as the informational messages are not errors or packaging
bugs.

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

Comment 2 w unruh 2023-03-15 22:40:29 CET
But dracut after a new kernel was loaded has no such "warning" messages. It was only when the microcode was installed that these messages popped up.  Ie, this message only occured when the microcode was loaded. (The new kernels were installed after the new microcode was installed.)

I will change back to  reopened so that I can see any response to the above.
I am glad to hear that these are just warnings, since there is no indication in the messages that these are ignorable.

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)

Comment 3 Dave Hodgins 2023-03-16 00:23:24 CET
My mistake. I'm pretty sure that at one time the kernel packages also generated
the messages, but could be wrong about that.

When installing a kernel, the postinstall scriptlet for kernel packages calls
/sbin/installkernel which calls /usr/sbin/bootloader-config which calls
/usr/lib/libDrakX/bootloader.pm, which calls /usr/bin/mkinitrd which calls
dracut but suppresses it's output with ...
            dracut $dracut_args --add-drivers "$basicmodules" "$target" \
                "$kernel" &>/dev/null

When installing microcode, "rpm -q --scripts microcode" shows it's calling
dracut directly from a postinstall scriptlet, without suppressing it's output.

Either way it's not a bug, but a choice of the developers.

Re-closing. Please reopen as a cosmetic enhancement for the microcode package
in cauldron if you think the scriptlet should suppress the dracut output just
like the kernel packages do, or for the dracut package if you think the
messages should not be suppressed when installing the kernel packages, or
leave closed if it doesn't matter to you.

Note that comments added to closed bug reports still get copied to everyone
on the bug cc list. It's not necessary to re-open to add bug comments.

Status: REOPENED => RESOLVED
Resolution: (none) => INVALID