lxd containers have become degraded

[Dimitri John Ledkov]

20170920 container boots degraded with
Oct 13 10:09:28 test20170920 systemd[256]: systemd-hostnamed.service: Failed at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied

20170919 container boots non-degraded. Package list changes are insignificant.

[Dave Chiluk (chiluk)]

Verified kind of still exists with ubuntu 17.10 amd64 (daily) (20180227)

# journalctl -u systemd-hostnamed.service
-- Logs begin at Wed 2018-02-28 16:38:35 UTC, end at Wed 2018-02-28 16:39:16 UTC. --
Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Failed to reset devices.list: Operation not permitted
Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Failed to set invocation ID on control group /system.slice/systemd-hostnamed.service, ig
Feb 28 16:38:51 pants systemd[1]: Starting Hostname Service...
Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK
Feb 28 16:38:51 pants systemd[1]: Failed to start Hostname Service.
Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Unit entered failed state.
Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'.

However I'm not sure where @xnox saw the "degraded" status

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Dave Chiluk (chiluk)]

Same thing in bionic

# journalctl -u systemd-hostnamed
-- Logs begin at Wed 2018-02-28 16:43:47 UTC, end at Wed 2018-02-28 16:44:28 UTC. --
Feb 28 16:44:03 bionic systemd[1]: systemd-hostnamed.service: Failed to reset devices.list: Operation not permitted
Feb 28 16:44:03 bionic systemd[1]: systemd-hostnamed.service: Failed to set invocation ID on control group /system.slice/systemd-hostnamed.service, ignoring: Ope
Feb 28 16:44:03 bionic systemd[1]: Starting Hostname Service...
Feb 28 16:44:03 bionic systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK
Feb 28 16:44:03 bionic systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'.
Feb 28 16:44:03 bionic systemd[1]: Failed to start Hostname Service.

[Scott Moser (smoser)]

root@b3:~# systemctl --no-pager | grep failed
● sys-kernel-config.mount loaded failed failed Kernel Configuration File System
● systemd-hostnamed.service loaded failed failed Hostname Service
● systemd-modules-load.service loaded failed failed Load Kernel Modules
root@b3:~# cat /etc/cloud/build.info
build_name: server
serial: 20180406

[Scott Moser (smoser)]

Quite a pleasent surprise I found today.

$ lxc launch ubuntu-daily:devel devel1
$ sleep 20
$ lxc exec devel1 systemctl status | grep State
    State: running

$ lxc exec devel1 -- sh -c 'cat /etc/cloud/build.info; lsb_release -sc'
build_name: server
serial: 20190531
eoan

$ lxc exec devel1 -- systemctl status --no-pager
● devel1
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Fri 2019-05-31 14:58:48 UTC; 3min 32s ago
   CGroup: /
           ├─1204 systemctl status --no-pager
           ├─init.scope
           │ └─1 /sbin/init
           └─system.slice
             ├─systemd-networkd.service
             │ └─135 /lib/systemd/systemd-networkd
             ├─systemd-udevd.service
             │ └─87 /lib/systemd/systemd-udevd
             ├─cron.service
             │ └─185 /usr/sbin/cron -f
             ├─polkit.service
             │ └─222 /usr/lib/policykit-1/polkitd --no-debug
             ├─networkd-dispatcher.service
             │ └─187 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-star...
             ├─accounts-daemon.service
             │ └─180 /usr/lib/accountsservice/accounts-daemon
             ├─systemd-journald.service
             │ └─58 /lib/systemd/systemd-journald
             ├─atd.service
             │ └─198 /usr/sbin/atd -f
             ├─unattended-upgrades.service
             │ └─256 /usr/bin/python3 /usr/share/unattended-upgrades/unattend...
             ├─ssh.service
             │ └─200 /usr/sbin/sshd -D
             ├─snap-core-6964.mount
             │ └─472 snapfuse /var/lib/snapd/snaps/core_6964.snap /snap/core/...
             ├─snapd.service
             │ └─502 /usr/lib/snapd/snapd
             ├─rsyslog.service
             │ └─181 /usr/sbin/rsyslogd -n -iNONE
             ├─console-getty.service
             │ └─213 /sbin/agetty -o -p -- \u --noclear --keep-baud console 1...
             ├─snap-lxd-10756.mount
             │ └─672 snapfuse /var/lib/snapd/snaps/lxd_10756.snap /snap/lxd/1...
             ├─systemd-resolved.service
             │ └─137 /lib/systemd/systemd-resolved
             ├─dbus.service
             │ └─184 /usr/bin/dbus-daemon --system --address=systemd: --nofor...
             └─systemd-logind.service
               └─188 /lib/systemd/systemd-logind

[Dimitri John Ledkov (xnox)]

That particular issue is gone, but there are others now

# systemctl list-units --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