Got this bug again on other xenial system.

Here is a log:
$ cat /var/log/syslog | grep break
Aug 23 13:55:13 hostname systemd[1]: nbd-client.service: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
sysinit.target/start
Aug 24 01:17:38 hostname systemd[1]: cups.socket: Job cups.socket/start deleted 
to break ordering cycle starting with sockets.target/start
Aug 24 01:17:38 hostname systemd[1]: nbd-client.service: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
sockets.target/start
Aug 24 01:17:38 hostname systemd[1]: network-online.target: Job 
network-online.target/start deleted to break ordering cycle starting with 
sockets.target/start
Aug 24 01:17:38 hostname systemd[1]: network.target: Job network.target/start 
deleted to break ordering cycle starting with sockets.target/start
Aug 24 01:17:38 hostname systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start deleted to break ordering cycle starting with 
sockets.target/start

This results offline system. I need manually start networkmanager
service.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582986

Title:
  NetworkManager service does not start during bootup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to