[Bug 1723390] Re: lxd containers have become degraded
Dave Chiluk
1723390 at bugs.launchpad.net
Wed Feb 28 16:50:37 UTC 2018
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.
--
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
More information about the foundations-bugs
mailing list