c) lnet.service fails to start without dkms
(not a blocker)
$ systemctl status lnet.service 
× lnet.service - lnet management
     Loaded: loaded (/usr/lib/systemd/system/lnet.service; enabled; preset: 
enabled)
     Active: failed (Result: exit-code) since Fri 2026-11-13 17:31:00 UTC; 6s 
ago
 Invocation: a824a8032fc444158f5fe743a17e8c6c
    Process: 31375 ExecStart=/sbin/modprobe lnet (code=exited, status=1/FAILURE)
   Main PID: 31375 (code=exited, status=1/FAILURE)
   Mem peak: 2.2M
        CPU: 13ms

Nov 13 17:31:00 r-lustre systemd[1]: Starting lnet.service - lnet management...
Nov 13 17:31:00 r-lustre modprobe[31375]: modprobe: FATAL: Module lnet not 
found in directory /lib/modules/7.0.0-43-generic

It should depend on the dkms package, or perhaps have a condition to not
start if the kernel module isn't available (could the module come from
another package perhaps?)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2169885

Title:
  [SRU] Please backport lustre 2.17.58+dfsg-0ubuntu2 from stonking to
  resolute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lustre/+bug/2169885/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to