Red Hat Bugzilla – Bug 990994
systemd-206 requires kmod-14
Last modified: 2013-09-13 07:39:38 EDT
Description of problem:
The 'kmod-static-nodes' service added to systemd-206 invokes
'/usr/bin/kmod static-nodes ...', which is new to kmod-14, but
systemd does not have a Requires on kmod-14 .
Version-Release number of selected component:
'rpm' does not complain if a system with kmod-13 is upgraded to systemd-206 .
But that combination will produce the following message at boot time:
Failed to start Create list of required static device nodes for the current kernel.
because the new /usr/lib/systemd/system/kmod-static-nodes.service invokes:
ExecStart=/usr/bin/kmod static-nodes --format=tmpfiles --output=/run/tmpfiles.d/kmod.conf
and the 'static-nodes' command first appeared in kmod version 14 .
Granted that this is (was) likely to happen only on a Frankensystem (new parts
and old parts); nonetheless, the requirement is clearly there.
FIX: This should be added to the systemd spec file:
Requires: kmod >= 14
Yep, it's on README (one commmit after 206).
The requirement will probably be bumped again once kmod 15 is released, since the plan is to drop ExecStartPre from the service file.
Can someone remind me why are we shipping that unit in the systemd when it truly belongs in kmod and can affect container setups?
That was discussed in the same thread
and modified in kmod git
Fixed in fedora systemd git.