Didn't mean to blame systemd-modules-load.service specifically; as you point out, it's just where the smoking gun appears. I suppose the only thing that's debatable is whether it should fail in these circumstances and whether it would inhibit other, unrelated, modules to load? (that would be bad)
Also FWIW, as noted on the investigations in the 'ask' question, /etc /modules-load.d/modules.conf is empty as is /usr/lib/modules-load.d. I haven't managed to work out what is triggering this particular module to be considered for loading. A grep for 'ib_iser' in /var/log reveals nothing beside what's in the report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566468 Title: systemd-modules-load.service: Failing due to missing module 'ib_iser' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1566468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
