[Bug 1209497] New: openQA test fails for autoyast installation on s390x
https://bugzilla.suse.com/show_bug.cgi?id=1209497 Bug ID: 1209497 Summary: openQA test fails for autoyast installation on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers@suse.de Reporter: sofia.syrianidou@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 865665 --> https://bugzilla.suse.com/attachment.cgi?id=865665&action=edit xml profiles While the autoyast installation seems to proceed successfully, at the point that the system is preparing for initial boot, there is a failure, the screen turns black and the hypervisor fails to reconnect to the SUT. Unfortunately, I don't have the resources to reproduce manually and the openqa test is unreachable so logs are not collected. attached: zvm.xml - is the xml profiles used for the test zvm-cloned.xml - is the cloned xml profile from another s390x test, for comparison (the cloned one cannot be used because the system demonstrates error for partitioning) ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-s390x-autoyast_zvm@s390x-zVM-vswitch-l2 fails in [installation](https://openqa.opensuse.org/tests/3161276/modules/installation/steps/21) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse&flavor=DVD&machine=s390x-zVM-vswitch-l2&test=autoyast_zvm&version=Tumbleweed) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c1 --- Comment #1 from Stefan Hundhammer <shundhammer@suse.com> --- Created attachment 865669 --> https://bugzilla.suse.com/attachment.cgi?id=865669&action=edit Screenshot: Last message in installer Qt UI "Prepare system for initial boot", and then the screen goes black. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c2 --- Comment #2 from Stefan Hundhammer <shundhammer@suse.com> --- Created attachment 865671 --> https://bugzilla.suse.com/attachment.cgi?id=865671&action=edit Screenshot: Installer shutting down, ssh connection closed -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c3 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nikolay.gueorguiev@suse.com Flags| |needinfo?(nikolay.gueorguie | |v@suse.com) --- Comment #3 from Stefan Hundhammer <shundhammer@suse.com> --- There is not much that we can do without y2logs or anything. All the video tells us is that the installer is finished, there was no error, and the ssh connection was shut down, as is usual for a reboot. Nikolay, could you try to reproduce this and do some further investigations? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c4 --- Comment #4 from Stefan Hundhammer <shundhammer@suse.com> --- There is a login prompt on the serial console at serial0.txt here: https://openqa.opensuse.org/tests/3161276/logfile?filename=serial0.txt openSUSE Tumbleweed Installation s390linux144 login: Not sure if that was during the installation, or after the reboot. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(nikolay.gueorguie | |v@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Comment #5 is|1 |0 private| | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c6 --- Comment #6 from Stefan Hundhammer <shundhammer@suse.com> --- You are right, there are those XIO errors; but I don't think they are the same problem as in bug #1206585: I am pretty sure that it's simply the X server shutting down that the y2start script started. It's normal that the X server is terminated after the first part of the installation is done, just before the reboot. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c7 --- Comment #7 from Stefan Hundhammer <shundhammer@suse.com> --- But that reminds me that even our s/390 experts had a hard time getting an X11-based installation to work (bug #1206585); back then we suspected a network connection that had become too complex, with possibly timeouts accumulating, causing XIO errors. So reproducing this scenario manually will probably not work. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c8 --- Comment #8 from Stefan Hundhammer <shundhammer@suse.com> --- This openQA test does not collect y2logs before the reboot, so I don't see a way to investigate this any further. Is it a problem with the console being redirected to a serial port? A kernel crash? A bootloader failure? From what point on should the openQA framework give us any kind of feedback if any of those things happened? I don't know. What we do know, however, is that the YaST installation did not throw an error, and it didn't crash unexpectedly. So I don't believe that this is a YaST bug until proven otherwise. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c9 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #9 from Stefan Hundhammer <shundhammer@suse.com> --- So, even if we do get y2logs with possibly some modification of the openQA test (to upload them when all the other stuff is also uploaded, which seemed to work fine according to autoinst-log.txt), that won't give us any more information: We'll see the preparation to reboot, and that will be the last sign of life. So I guess somebody will have to get near the machine (in the same network segment to exclude network problems) and retry it manually and watch what happens; if it even tries to reboot, if there are bootloader or kernel messages. Right now we don't see any of them. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c10 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sofia.syrianidou@suse.com Flags| |needinfo?(sofia.syrianidou@ | |suse.com) --- Comment #10 from Lukas Ocilka <locilka@suse.com> --- As I see it after looking at https://openqa.opensuse.org/tests/3161276# - The Installer has finished its job. Although the test failed in "autoyast -> installation" section, it's IMO just a naming issue as what happens after installing the system is not in our hands anymore, especially not on S390. Sofia, please, investigate further, reproduce manually, provide before-reboot logs. Or reassign to Booting issues if you can't. We can't. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c11 Sofia Syrianidou <sofia.syrianidou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sofia.syrianidou@ | |suse.com) | --- Comment #11 from Sofia Syrianidou <sofia.syrianidou@suse.com> --- Sorry for the long wait. I managed to collect some logs. The VM setup is a bit peculiar here and the installer is facing difficulties to propose a partitioning if I format the disk before installation or if I use a cloned profile partitioning in aytoyast profile. The vm is running inside a container. Please find the logs here: https://openqa.opensuse.org/tests/3193709/logfile?filename=serial_terminal.t... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c12 --- Comment #12 from Sofia Syrianidou <sofia.syrianidou@suse.com> --- In the latest run, I see some additional logs: https://openqa.opensuse.org/tests/3194990#step/installation/25 It seems to me that reboot is happening but installation has not finished properly /usr/lib64/ruby/vendor_ruby/3.2.0/yast/scr.rb:113: warning: undefining the allocator of T_DATA class Yast::YCode -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 Sofia Syrianidou <sofia.syrianidou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c13 --- Comment #13 from Lukas Ocilka <locilka@suse.com> --- (In reply to Sofia Syrianidou from comment #12)
/usr/lib64/ruby/vendor_ruby/3.2.0/yast/scr.rb:113: warning: undefining the allocator of T_DATA class Yast::YCode
This is a harmless warning. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c14 --- Comment #14 from Stefan Hundhammer <shundhammer@suse.com> --- So now we also have the log from the serial console. We can see that the installation finished successfully, and that's the end of it. We don't see it come up using the serial console after the reboot. That is a bit of information (quite literally a bit), but nothing more. Now we know that the system is not just trying to communicate with us on the serial console. Other than that, we are not much better off than before. It doesn't come up. Why, we don't know. And we (the YaST team) have no way to find out from the existing information. I was hoping that somebody who knows a bit more about s/390 machines can use some s/390 tools to figure out what is happening. On the PC architecture, we could watch the hardware / BIOS self test and see what the BIOS is trying to do; if it tries to start an OS, and from what disk / what partition. There would be messages. Does it get to the Grub2 stage? Does it get to starting to load an OS from Grub2? What's happening? We don't know. Unless somebody with more s/390 know-how can continue investigating here, I don't see how to continue here. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c15 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(nikolay.gueorguie | |v@suse.com) --- Comment #15 from Stefan Hundhammer <shundhammer@suse.com> --- Nikolay, you are our last hope here. Otherewise I fear we'll have to close this with an unsatisfactory status like WONTFIX or similar. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c16 Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(nikolay.gueorguie | |v@suse.com) | --- Comment #16 from Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> --- (In reply to Stefan Hundhammer from comment #15)
Nikolay, you are our last hope here.
Otherewise I fear we'll have to close this with an unsatisfactory status like WONTFIX or similar.
I did some tests (manually) with autoyast and autoyast2. I did few installations of Tumbleweed on s390x with autoyast and autoyast2. I had some issues to set a proper "environment": ftp server, http server, parmfile and so, but at the end autoinstall worked. There were "partitioning errors", but after updating the "cloned" .xml file, adding <dasd>...</dasd> section after the </bootloader>, e.g. <dasd t="map"> <devices t="list"> <listentry t="map"> <channel>0.0.0150</channel> <diag t="boolean">false</diag> <format t="boolean">false</format> </listentry> <listentry t="map"> <channel>0.0.0160</channel> <diag t="boolean">false</diag> <format t="boolean">false</format> </listentry> </devices> <format_unformatted t="boolean">false</format_unformatted> </dasd> I didn't use serial consoles, I was using only the x3270 console. In the x3270 console you could see the very beginning of the IPL-ing or booting process. Might be few screenshots taken from x3270 "green screens" could help... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209497 https://bugzilla.suse.com/show_bug.cgi?id=1209497#c17 Sofia Syrianidou <sofia.syrianidou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #17 from Sofia Syrianidou <sofia.syrianidou@suse.com> --- I have also used the <dasd> blocks but I assume there must be an issue with our setup for opensuse testing. Let's close this bug. Thanks everyone for the input. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com