On Thu, May 07, Andrei Borzenkov wrote:
В Wed, 6 May 2015 20:26:11 +0200 Olaf Hering <olaf@aepfle.de> пишет:
For me network is broken, tested only booting a dom0. 'systemctl start wicked.service' started the network as expected. My guess: there are wrong Before=/After= lines in various .services:
root@optiplex:~ # journalctl -b | grep delete Mai 06 20:05:25 optiplex systemd[1]: Job NetworkManager-wait-online.service/start deleted to break ordering cycle starting with network.target/start Mai 06 20:05:25 optiplex systemd[1]: Job NetworkManager.service/verify-active deleted to break ordering cycle starting with network.target/start Mai 06 20:05:25 optiplex systemd[1]: Job wicked.service/start deleted to break ordering cycle starting with network.target/start Mai 06 20:05:25 optiplex systemd[1]: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start Mai 06 20:05:28 optiplex systemd[1]: Job YaST2-Second-Stage.service/start deleted to break ordering cycle starting with NetworkManager.service/verify-active Mai 06 20:05:28 optiplex systemd[1]: Job NetworkManager-wait-online.service/start deleted to break ordering cycle starting with NetworkManager.service/verify-active Mai 06 20:05:29 optiplex systemd[1]: Job xinetd.service/start deleted to break ordering cycle starting with NetworkManager.service/verify-active Mai 06 20:05:29 optiplex systemd[1]: Job network.target/start deleted to break ordering cycle starting with NetworkManager.service/verify-active Mai 06 20:05:29 optiplex systemd[1]: Job xenstored.socket/start deleted to break ordering cycle starting with sockets.target/start Mai 06 20:05:29 optiplex systemd[1]: Job proc-xen.mount/start deleted to break ordering cycle starting with sockets.target/start Mai 06 20:05:29 optiplex systemd[1]: Job sockets.target/start deleted to break ordering cycle starting with sockets.target/start Mai 06 20:05:29 optiplex systemd[1]: Job wicked.service/start deleted to break ordering cycle starting with YaST2-Firstboot.service/start Mai 06 20:06:33 optiplex /usr/lib/gdm/gdm-x-session[1534]: Entry deleted from font path. Any chance http://bugzilla.suse.com/show_bug.cgi?id=905639 is related?
No idea. This morning I got this while booting kernel-default, and the network came up. Looks like booting a dom0 makes it worse. root@optiplex:~ # journalctl -b | grep delete Mai 07 08:10:52 optiplex systemd[1]: Job YaST2-Second-Stage.service/start deleted to break ordering cycle starting with YaST2-Firstboot.service/start Mai 07 08:10:52 optiplex systemd[1]: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start Mai 07 08:10:55 optiplex systemd[1]: Job NetworkManager.service/verify-active deleted to break ordering cycle starting with network.target/start Mai 07 08:10:56 optiplex systemd[1]: Job YaST2-Firstboot.service/start deleted to break ordering cycle starting with network.target/start Mai 07 08:10:56 optiplex systemd[1]: Job YaST2-Second-Stage.service/start deleted to break ordering cycle starting with network.target/start Mai 07 08:10:56 optiplex systemd[1]: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start Mai 07 08:11:43 optiplex systemd[1]: Job NetworkManager.service/verify-active deleted to break ordering cycle starting with network.target/start Mai 07 08:11:43 optiplex systemd[1]: Job YaST2-Firstboot.service/start deleted to break ordering cycle starting with wicked.service/start Mai 07 08:11:43 optiplex systemd[1]: Job YaST2-Second-Stage.service/start deleted to break ordering cycle starting with wicked.service/start Mai 07 08:12:14 optiplex /usr/lib/gdm/gdm-x-session[2165]: Entry deleted from font path. To get YaST2 out of the picture I think both units should just depend on network.service, which is provided by wicked.service and NetworkManager.service. I wonder if it just happens to work for all of us because most boot kernel-default. Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org