http://bugzilla.novell.com/show_bug.cgi?id=954908 http://bugzilla.novell.com/show_bug.cgi?id=954908#c8 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(fvogt@suse.com) --- Comment #8 from Stefan Schubert <schubi@suse.com> --- (In reply to Marius Tomaschewski from comment #6)

(In reply to Stefan Schubert from comment #4)

...

Thanks, I can reproduce the bug. The installation workflow hangs while starting the network via "rcnetwork start".

I cannot see anything like this -- where? I cannot see any usable log files attached -- there is not even y2log (only ./YaST2/y2log-1.gz).

That's because YaST is not really started at all. Just see y2start where it is hanging

...

So I assume that is around wickedd.

I don't think so. I'd is about systemd dependencies in Firstboot.service and Yast2-Second-Stage.service services (causing some loop/deadlock).

IMO there was already an another (SLE-12-SP1) bug about. [Further, yast2 should IMO use a Yast2-Second-Stage.target, so the system boots into this special target. When the configuration is done, boot default.target and not break start dependencies scheduled in systemd, but canceled due to random calls of "systemctl restart --ignore-dependencies ..." by yast2.]

(In reply to Thomas Renninger from comment #5)

...

Pawel, Marius. Could someone have a look at this one, please.

Schubi: Afaik this only happens with normal auto installation. Can you provide a hint how to run into this and how to debug this remotely if possible or does one have to reproduce on a local machine and then switch to an available console?

Add systemd.log_level=debug systemd.log_target=kmsg to kernel boot parameters call "journalctl -b -o short-precise > journal.txt" and attach journal.txt.

To get a wicked logs, set WICKED_DEBUG=all in /etc/sysconfig/network/config.

I think that's a question to the reporter too:-) -- You are receiving this mail because: You are on the CC list for the bug.