![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=902464 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sysadmin@lnt.ei.t | |um.de) --- Comment #34 from Thomas Blume <thomas.blume@suse.com> --- (In reply to LNT Sysadmin from comment #33)
(In reply to Thomas Blume from comment #32)
It looks like /usr/lib/YaST2/bin/testX hangs.
Yes, testX hangs, but only sometimes! There is definitely a problem here.
It does not happen with every time I boot the VM from this state. Sometimes testX passes, but then the installation will wait for the network to come up. You can simulate this by killing testX via "pkill testX".
So testX definitely has a problem, but it could probably be another issue, as the network does not come up anyways, even if testX succeeds or gets killed.
Ok, I see the problem. When I kill all testX processes, /system.slice/YaST2-Second-Stage.service continues. It tries do download some packages from the network, but this obviously fails, because the network isn't up. If I skip this download, the installation finishes and the network gets set up. So, the wickedd.service must not wait for YaST2-Second-Stage.service. Checking the dependencies of YaST2-Second-Stage.service, I see this: -->-- Before=getty@tty1.service display-manager.service network.service NetworkManager.service SuSEfirewall2_init.service SuSEfirewall2.service --<-- Obviously, having network.service in a Before statement is not a good idea, if YaST2-Second-Stage.service wants to download some files from the network. I've modified the Before Statement like this: Before=getty@tty1.service display-manager.service and made the same for YaST2-Firstboot.service. This made wicked start up correctly: -->-- wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled) Active: active (exited) since Fri 2015-05-22 09:59:41 CEST; 4min 9s ago Process: 936 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 936 (code=exited, status=0/SUCCESS) CGroup: /system.slice/wicked.service May 22 09:59:41 linux-sjs0 wicked[936]: lo up May 22 09:59:41 linux-sjs0 wicked[936]: eth0 setup-in-progress --<-- Can you try wheter it works on your side as well? -- You are receiving this mail because: You are on the CC list for the bug.