systemd-modules-load.service: Failing due to missing module 'ib_iser'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Tim Gardner | ||
Xenial |
Fix Released
|
Medium
|
Tim Gardner | ||
linux-kvm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned | ||
linux-raspi2 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned | ||
open-iscsi (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Xenial |
Invalid
|
Medium
|
Unassigned |
Bug Description
On a number of VMs using Xenial daily builds 20160330 and 20160403, out of the box (just after booting for the first time), the following appears in dmesg at boot time:
systemd[1]: systemd-
systemd[1]: Failed to start Load Kernel Modules.
systemd[1]: systemd-
systemd[1]: systemd-
The following related complaint appears in /var/log/syslog:
ubuntu systemd-
ubuntu systemd-
It looks like 'ib_iser' is some Mellanox-related module, which I don't *think* is something that a stock cloudimg install should attempt to load but I may be wrong; in any case, it's not present (nor is there any similar whingeing) on similar VMs running off 14.04 cloudimg.
---
root@testvm4:~# lsb_release -rd
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
root@testvm4:~# apt policy systemd
systemd:
Installed: 229-3ubuntu2
Candidate: 229-3ubuntu2
CVE References
affects: | cloud-init (Ubuntu) → open-iscsi (Ubuntu) |
Changed in open-iscsi (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
status: | Confirmed → In Progress |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
Changed in open-iscsi (Ubuntu Xenial): | |
status: | Confirmed → Invalid |
tags: | added: cscc |
Well, don't shoot the messenger :-) ib_iser.ko is in linux-image-extra which we (consciously) don't install on cloud images. So please fix the cloud image builds or cloud-init (whichever it is) to not add the module to /etc/modules by default, unless you actually install linux-image-extra.