[Bug 825728] New: When installing with autoyast over serial console, second stage does not run
https://bugzilla.novell.com/show_bug.cgi?id=825728 https://bugzilla.novell.com/show_bug.cgi?id=825728#c0 Summary: When installing with autoyast over serial console, second stage does not run Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bmaloney@vtti.vt.edu QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36 When I install via autoyast with parameters console=ttyS0,115200 textmode=1, the first stage of the installation proceeds normally, however after reboot, rather than going into stage 2, I get the following prompt: Welcome to openSUSE 12.3 "Dartmouth" - Kernel 3.7.10-1.16-default (ttyS0). linux login: I am working around this by turning off the serial console in a chroot-script and turning it back on in a post-script. I have not confirmed whether this is an autoyast issue or general installation issue. I do have <second_stage config:type="boolean">true</second_stage> in my autoyast config. Reproducible: Always Steps to Reproduce: 1. Install with autoyast and console=ttyS0 2. 3. Actual Results: Second stage installation does not run. Expected Results: Second stage installation should run and reboot into final system. Here are the full messages from the boot that should go to second stage: doing fast boot Creating device nodes with udev 6 logical volume(s) in volume group "LVM" now active 6 logical volume(s) in volume group "LVM" now active 6 logical volume(s) in volume group "LVM" now active Waiting for device /dev/mapper/LVM-root to appear: ok fsck from util-linux 2.21.2 [/sbin/fsck.xfs (1) -- /] fsck.xfs -a /dev/mapper/LVM-root /sbin/fsck.xfs: XFS file system. fsck succeeded. Mounting root device read-write. Mounting root /dev/mapper/LVM-root mount -o rw,defaults -t xfs /dev/mapper/LVM-root /root fsck from util-linux 2.21.2 [/sbin/fsck.xfs (1) -- /dev/mapper/LVM-usr] fsck.xfs -a /dev/mapper/LVM-usr /sbin/fsck.xfs: XFS file system. Mounting /usr systemd-fsck[556]: /sbin/fsck.xfs: XFS file system. systemd-fsck[553]: /sbin/fsck.xfs: XFS file system. systemd-fsck[555]: /sbin/fsck.xfs: XFS file system. systemd-fsck[554]: /sbin/fsck.xfs: XFS file system. systemd-fsck[560]: /dev/sda1: clean, 319/52000 files, 40380/207872 blocks Failed to issue method call: Unit SuSEfirewall2.service not loaded. GProbing connected terminal... Initializing virtual console... Found a Linux console terminal on /dev/console (150 columns x 49 lines). redirecting to "systemctl --ignore-dependencies start network.service" Welcome to openSUSE 12.3 "Dartmouth" - Kernel 3.7.10-1.16-default (ttyS0). linux login: -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825728 https://bugzilla.novell.com/show_bug.cgi?id=825728#c Ye Yuan <yyuan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |fehr@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825728 https://bugzilla.novell.com/show_bug.cgi?id=825728#c2 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bmaloney@vtti.vt.edu --- Comment #2 from Thomas Fehr <fehr@suse.com> 2013-06-20 03:27:19 UTC --- I have another bug report (bnc#823224) where second stage of an autoyast install does not get started. So far I have not much clue when and how this happens (which probably is because i am more or less clueless about systemd). So far I was unable to reproduce such a problem locally to investigate that further. What happens if you do a normal (non-autoyast) installation with console=ttyS0? Does second stage YaST get started there? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825728 https://bugzilla.novell.com/show_bug.cgi?id=825728#c3 --- Comment #3 from Thomas Fehr <fehr@suse.com> 2013-06-20 03:47:31 UTC --- Another idea: since the other system with the same problem is headless and yours uses serial console I have some suspects against package plymouth (which is responsible for graphical boot animation). Could you try if behavior of your autoyast install changes when you add plymouth to the list of packages not to install: <software> . . <remove-packages> <package>plymouth</package> </remove-packages> </software> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825728 https://bugzilla.novell.com/show_bug.cgi?id=825728#c4 Brian Maloney <bmaloney@vtti.vt.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bmaloney@vtti.vt.edu | --- Comment #4 from Brian Maloney <bmaloney@vtti.vt.edu> 2013-06-20 10:02:29 UTC --- Doing a non-autoyast install over serial has the same effect. Your plymouth idea was a good one. Remove-packages didn't change anything but adding plymouth to the <packages> section improved the situation. With plymouth added, it starts the second stage of YaST, but the second stage never completes. Eventually the login prompt also shows up. When I try to ctrl-alt-delete the system, it gives a message about "Stopping YaST2 Second Stage" and hangs there. Another thing I noticed about doing serial installs - not only does it not include plymouth, but I also had to add a bunch of yast2- packages to my AutoYAST profile for the second stage to run even on the VGA console after a first stage done over serial. For some reason installation over serial seems to make some incorrect assumptions about things the system won't need. Hope this information helps! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825728 https://bugzilla.novell.com/show_bug.cgi?id=825728#c5 --- Comment #5 from Thomas Fehr <fehr@suse.com> 2013-06-20 10:40:44 UTC --- I meanwhile have a setup with using VirtualBox, socat and screen that nicely emulates serial console behavior and I can now finally reproduce the problem here. So far I still have not much clue what really causes the problem. It seems somehow the shell that executes /usr/lib/YaST2/startup/YaST2.Second-Stage aborts. This can be seen at file /var/log/YaST2/y2start.log, it aborts at different lines in each test, but always aborts before real yast gets started. Will continue investing this next week. Regarding package selection: Here you are more or less on your own with autoyast, there is not the same automatism in place as in interactive yast. So I would be surprised if the same autoyast.xml file would result in different packages installed regardless of installing via serial console or not (of course if the bug that second stage is not called would not be there). For my testing, I mostly use <patterns config:type="list"> <pattern>enhanced_base</pattern> </patterns> In my software section, this provides most of the expected packages but still gives a quite small disk footprint and a fast install time. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825728 https://bugzilla.novell.com/show_bug.cgi?id=825728#c6 --- Comment #6 from Thomas Fehr <fehr@suse.com> 2013-06-24 07:33:33 UTC --- It seems that due to the different startup in 12.3 compared to 12.2 there a cases where someone (no idea if its kernel or systemd) sends s signal SIGHUP to the shell executing YaST2-Second-Stage.service (you can verify this by looking at /var/log/YaST2/y2start.log compared with a successful file it aborts somewhere before yast2 gets actually started). To fix that, it would probably be easiest to use a script to make YaST2.Second-Stage ignore SIGHUP. <scripts> <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <interpreter>shell</interpreter> <source><![CDATA[ sed -i '/set -x/a\\ntrap \"\" SIGHUP' /usr/lib/YaST2/startup/YaST2.Second-Stage ]]></source> </script> </chroot-scripts> </scripts> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825728 https://bugzilla.novell.com/show_bug.cgi?id=825728#c7 --- Comment #7 from Brian Maloney <bmaloney@vtti.vt.edu> 2013-06-24 09:51:33 UTC --- Thanks very much Thomas, that workaround allows my second stage to complete. If there's anything else you need from me to move this ticket towards a final fix, please let me know. (In reply to comment #6)
It seems that due to the different startup in 12.3 compared to 12.2 there a cases where someone (no idea if its kernel or systemd) sends s signal SIGHUP to the shell executing YaST2-Second-Stage.service (you can verify this by looking at /var/log/YaST2/y2start.log compared with a successful file it aborts somewhere before yast2 gets actually started).
To fix that, it would probably be easiest to use a script to make YaST2.Second-Stage ignore SIGHUP.
<scripts> <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <interpreter>shell</interpreter> <source><![CDATA[ sed -i '/set -x/a\\ntrap \"\" SIGHUP' /usr/lib/YaST2/startup/YaST2.Second-Stage ]]></source> </script> </chroot-scripts> </scripts>
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825728 https://bugzilla.novell.com/show_bug.cgi?id=825728#c8 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #8 from Thomas Fehr <fehr@suse.com> 2013-06-24 09:55:17 UTC --- Thanks for verification, setting to fixed then. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825728 https://bugzilla.novell.com/show_bug.cgi?id=825728#c9 Ahmon Dancy <dancy@dancysoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dancy@dancysoft.com --- Comment #9 from Ahmon Dancy <dancy@dancysoft.com> 2013-06-25 10:55:07 UTC --- For the record, noting my objection to the resolution of "FIXED" for this problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com