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
Verified kind of still exists with ubuntu 17.10 amd64 (daily) (20180227)
# journalctl -u systemd-hostnamed.servicehostnamed.service: Failed to reset devices.list: Operation not permittedhostnamed.service: Failed to set invocation ID on control group /system.slice/systemd-hostnamed.service, ighostnamed.service: Main process exited, code=exited, status=225/NETWORKhostnamed.service: Unit entered failed state.hostnamed.service: Failed with result 'exit-code'.
-- 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-
Feb 28 16:38:51 pants systemd[1]: systemd-
Feb 28 16:38:51 pants systemd[1]: Starting Hostname Service...
Feb 28 16:38:51 pants systemd[1]: systemd-
Feb 28 16:38:51 pants systemd[1]: Failed to start Hostname Service.
Feb 28 16:38:51 pants systemd[1]: systemd-
Feb 28 16:38:51 pants systemd[1]: systemd-
However I'm not sure where @xnox saw the "degraded" status