[Bug 1590641] [NEW] systemd-modules-load fails with monolithic kernel

[Alex King]

Public bug reported:

Out of the box on 16.04, when run with a monolithic kernel (i.e. non-
modular), /lib/systemd/systemd-modules-load bombs out.  This happens
even though there are only comments in the systemd-modules-load
configuration, i.e. there is nothing for it to do.

This causes systemd to regard the system state as degraded, because the
systemd-modules-load.service unit failed.

I suspect I could probably disable that unit, but then I would not be
able to boot back to a modular kernel and have initial module loading
work.

IMO, there should be a configuration option for systemd-modules-load to
allow a success return code if the kernel does not support loading
modules.  Or if that is not seen as a good fix, it should at least
succeed if it is not asked to load anything (i.e. empty config)

# lsb_release -rd
Description:	Ubuntu 16.04 LTS
Release:	16.04

systemd:
  Installed: 229-4ubuntu6
  Candidate: 229-4ubuntu6
  Version table:
 *** 229-4ubuntu6 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     229-4ubuntu4 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

I expect "systemctl" to show

    State: running
...
   Failed: 0 units

Instead I see:

    State: degraded
...
   Failed: 2 units

FYI I'm attaching apport data.  It's hard to use ubuntu-bug if you don't
have a ubuntu desktop.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "Apport data"
   https://bugs.launchpad.net/bugs/1590641/+attachment/4680108/+files/apport.systemd.a0im55y5.apport

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

Title:
  systemd-modules-load fails with monolithic kernel

Status in systemd package in Ubuntu:
  New

Bug description:
  Out of the box on 16.04, when run with a monolithic kernel (i.e. non-
  modular), /lib/systemd/systemd-modules-load bombs out.  This happens
  even though there are only comments in the systemd-modules-load
  configuration, i.e. there is nothing for it to do.

  This causes systemd to regard the system state as degraded, because
  the systemd-modules-load.service unit failed.

  I suspect I could probably disable that unit, but then I would not be
  able to boot back to a modular kernel and have initial module loading
  work.

  IMO, there should be a configuration option for systemd-modules-load
  to allow a success return code if the kernel does not support loading
  modules.  Or if that is not seen as a good fix, it should at least
  succeed if it is not asked to load anything (i.e. empty config)

  # lsb_release -rd
  Description:	Ubuntu 16.04 LTS
  Release:	16.04

  systemd:
    Installed: 229-4ubuntu6
    Candidate: 229-4ubuntu6
    Version table:
   *** 229-4ubuntu6 500
          500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
          100 /var/lib/dpkg/status
       229-4ubuntu4 500
          500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I expect "systemctl" to show

      State: running
  ...
     Failed: 0 units

  Instead I see:

      State: degraded
  ...
     Failed: 2 units

  FYI I'm attaching apport data.  It's hard to use ubuntu-bug if you
  don't have a ubuntu desktop.

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