[Bug 1811628] [NEW] Ubuntu 18.04 systemctl is-system-running always shows degraded in LXD containers

[Bryan Quigley]

Public bug reported:

Issue in Ubuntu 18.04 LTS:
lxc launch ubuntu-daily:18.04
lxc shell <containername>
# systemctl is-system-running
degraded

# systemctl --failed
  UNIT                         LOAD   ACTIVE SUB    DESCRIPTION                     
● sys-kernel-config.mount      loaded failed failed Kernel Configuration File System
● systemd-modules-load.service loaded failed failed Load Kernel Modules      

Fixed in Ubuntu 19.04:
lxc launch ubuntu-daily:19.04
lxc shell <containername>
systemctl is-system-running
running

It appears to be fixed by adding: ConditionVirtualization=!container to
both.  Can this be backported to 18.04 or are we stuck with special
casing 18.04 vs future versions?

As far as I know this is the easiest way to see if a container finished
starting.

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

-- 
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/1811628

Title:
  Ubuntu 18.04 systemctl is-system-running always shows degraded in LXD
  containers

Status in systemd package in Ubuntu:
  New

Bug description:
  Issue in Ubuntu 18.04 LTS:
  lxc launch ubuntu-daily:18.04
  lxc shell <containername>
  # systemctl is-system-running
  degraded

  # systemctl --failed
    UNIT                         LOAD   ACTIVE SUB    DESCRIPTION                     
  ● sys-kernel-config.mount      loaded failed failed Kernel Configuration File System
  ● systemd-modules-load.service loaded failed failed Load Kernel Modules      

  Fixed in Ubuntu 19.04:
  lxc launch ubuntu-daily:19.04
  lxc shell <containername>
  systemctl is-system-running
  running

  It appears to be fixed by adding: ConditionVirtualization=!container
  to both.  Can this be backported to 18.04 or are we stuck with special
  casing 18.04 vs future versions?

  As far as I know this is the easiest way to see if a container
  finished starting.

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