Bug 1214984 - kernel directory can not be found and systemd-network can not be installed (latest Tumbleweed update)
Summary: kernel directory can not be found and systemd-network can not be installed (l...
Status: RESOLVED INVALID
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: x86 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: systemd maintainers
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-05 09:09 UTC by Sarah Kriesch
Modified: 2023-09-05 16:52 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
dmesg (98.05 KB, text/x-log)
2023-09-05 09:13 UTC, Sarah Kriesch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sarah Kriesch 2023-09-05 09:09:12 UTC
I did a Tumpleweed update with "zypper dup" today.
I was a little bit surprised about the following error messages by depmod for the latest Linux kernel:


depmod: ERROR: could not open directory /var/tmp/weak-modules2.t7I1ge/6.4.12-1-default/usr/lib/modules/6.4.12-1-default: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod exited with error 1
depmod: ERROR: could not open directory /var/tmp/weak-modules2.t7I1ge/6.4.12-1-default/usr/lib/modules/6.4.12-1-default: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod exited with error 1
depmod: ERROR: could not open directory /var/tmp/weak-modules2.t7I1ge/6.4.12-1-default/usr/lib/modules/6.4.12-1-default: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod exited with error 1
depmod: ERROR: could not open directory /var/tmp/weak-modules2.t7I1ge/6.4.12-1-default/usr/lib/modules/6.4.12-1-default: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod exited with error 1
dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.4.12-1-default 6.4.12-1-default
dracut[I]: Module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found!
dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found!
dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found!
Comment 1 Sarah Kriesch 2023-09-05 09:13:27 UTC
Created attachment 869272 [details]
dmesg

the dmesg output
Comment 2 Michal Suchanek 2023-09-05 09:18:53 UTC
The depmod messages are noisy but the real problem is:

dracut[I]: Module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found!
dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found!
dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found!

so long as it is a problem at all, few people need network in the ramdisk.

Also the tool used for networking is typically NetworkManager, not networkd.
Comment 3 Sarah Kriesch 2023-09-05 09:26:52 UTC
Then I am happy, that we have got both options, that we can switch if one would not work.
Comment 4 Antonio Feijoo 2023-09-05 10:05:30 UTC
(In reply to Sarah Kriesch from comment #0)
> dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.4.12-1-default
> 6.4.12-1-default
> dracut[I]: Module 'systemd-networkd' will not be installed, because command
> 'networkctl' could not be found!
> dracut[I]: Module 'systemd-networkd' will not be installed, because command
> '/usr/lib/systemd/systemd-networkd' could not be found!
> dracut[I]: Module 'systemd-networkd' will not be installed, because command
> '/usr/lib/systemd/systemd-networkd-wait-online' could not be found!

Those are common messages due to dracut's high default verbosity.

If you want to add the systemd-networkd dracut module to the initrd, first you need to install the systemd-network package, but that does not seem to be your case, right?

So, if the depmod messages are just noise, I think we can close this bug.
Comment 5 Sarah Kriesch 2023-09-05 16:52:45 UTC
I wanted to report, if these error messages should not happen during the update process.
We can close this bug report, if it is not critical.