[Bug 954908] New: Boot after installation with AutoYaST hangs
http://bugzilla.suse.com/show_bug.cgi?id=954908 Bug ID: 954908 Summary: Boot after installation with AutoYaST hangs Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers@suse.de Reporter: fvogt@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After installing the latest tumbleweed snapshot with an AutoYaST XML, the system hangs on the first boot during the YaST start:
Probing connected terminal...
Initializing virtual console...
Found a Linux console terminal on /dev/console (122 columns x 55 lines).
and nothing happens. Adding " 3" to the kernel cmdline and running "systemctl disable" for YaST2-Firstboot.service and Yast2-Second-Stage.service makes it boot again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=954908
Fabian Vogt
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c5
Thomas Renninger
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c6
Marius Tomaschewski
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).
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. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=954908
Marius Tomaschewski
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c12
--- Comment #12 from Marius Tomaschewski
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c13
--- Comment #13 from Marius Tomaschewski
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c15
Stefan Schubert
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c16
Marius Tomaschewski
I have tried Marius suggestions but the result are the same. Marius which information is needed to go on ?
This is a question for systemd-maintainers how to solve this loop properly. I just wrote what I _think_ how it could work, but I'm not a systemd expert. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c17
Stefan Schubert
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c18
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c19
Martin Vidner
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c21
Thomas Blume
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c22
--- Comment #22 from Thomas Blume
IMHO, YaST2-Second-Stage shouldn't do an explicit network start. Instead some dependencies should be added that starts YaST2-Second-Stage.service after wicked.
After killing the network start processes (pid 3915 and 3938 in the screenshot), the installation finishes and the network is up. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=954908
Lars Marowsky-Bree
http://bugzilla.suse.com/show_bug.cgi?id=954908
Oliver Kurz
http://bugzilla.suse.com/show_bug.cgi?id=954908
http://bugzilla.suse.com/show_bug.cgi?id=954908#c28
Lars Marowsky-Bree
participants (1)
-
bugzilla_noreply@novell.com