[Bug 1723390] Re: lxd containers have become degraded

[Dave 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

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

Title:
  lxd containers have become degraded

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  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.

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