Observation¶

We have got a successful build of openSUSE Tumbleweed for s390x during the Christmas time.
openQA is failing in the first steps during the preparation of the bootloader and choosing the s320 console:

Test died: expected command exit status ok, got error at /usr/lib/os-autoinst/consoles/s3270.pm line 75, <$fh> line 22.¶

    consoles::s3270::send_3270(consoles::s3270=HASH(0x556b400f2428), "Connect(s390zl11.openqanet.opensuse.org)") called at /usr/lib/os-autoinst/consoles/s3270.pm line 315
    consoles::s3270::_connect_3270(consoles::s3270=HASH(0x556b400f2428), "s390zl11.openqanet.opensuse.org") called at /usr/lib/os-autoinst/consoles/s3270.pm line 360
    consoles::s3270::connect_and_login(consoles::s3270=HASH(0x556b400f2428)) called at /usr/lib/os-autoinst/consoles/s3270.pm line 424
    consoles::s3270::activate(consoles::s3270=HASH(0x556b400f2428)) called at /usr/lib/os-autoinst/consoles/console.pm line 55
    consoles::console::select(consoles::s3270=HASH(0x556b400f2428)) called at /usr/lib/os-autoinst/backend/baseclass.pm line 660
    backend::baseclass::try {...} () called at /usr/lib/perl5/vendor_perl/5.26.1/Try/Tiny.pm line 100
    eval {...} called at /usr/lib/perl5/vendor_perl/5.26.1/Try/Tiny.pm line 93
    Try::Tiny::try(CODE(0x556b4000b430), Try::Tiny::Catch=REF(0x556b408595e8)) called at /usr/lib/os-autoinst/backend/baseclass.pm line 664
    backend::baseclass::select_console(backend::s390x=HASH(0x556b40393d78), HASH(0x556b3fdf2ea8)) called at /usr/lib/os-autoinst/backend/baseclass.pm line 79
    backend::baseclass::handle_command(backend::s390x=HASH(0x556b40393d78), HASH(0x556b4089ff50)) called at /usr/lib/os-autoinst/backend/baseclass.pm line 616
    backend::baseclass::check_socket(backend::s390x=HASH(0x556b40393d78), IO::Handle=GLOB(0x556b40b26c28), 0) called at /usr/lib/os-autoinst/backend/s390x.pm line 41
    backend::s390x::check_socket(backend::s390x=HASH(0x556b40393d78), IO::Handle=GLOB(0x556b40b26c28), 0) called at /usr/lib/os-autoinst/backend/baseclass.pm line 284
    backend::baseclass::do_capture(backend::s390x=HASH(0x556b40393d78), undef, 1704270564.33364) called at /usr/lib/os-autoinst/backend/baseclass.pm line 311
    eval {...} called at /usr/lib/os-autoinst/backend/baseclass.pm line 311
    backend::baseclass::run_capture_loop(backend::s390x=HASH(0x556b40393d78)) called at /usr/lib/os-autoinst/backend/baseclass.pm line 133
    backend::baseclass::run(backend::s390x=HASH(0x556b40393d78), 14, 17) called at /usr/lib/os-autoinst/backend/driver.pm line 68
    backend::driver::__ANON__(Mojo::IOLoop::ReadWriteProcess=HASH(0x556b408938c8)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 329
    eval {...} called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 329
    Mojo::IOLoop::ReadWriteProcess::_fork(Mojo::IOLoop::ReadWriteProcess=HASH(0x556b408938c8), CODE(0x556b3f715d50)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 492
    Mojo::IOLoop::ReadWriteProcess::start(Mojo::IOLoop::ReadWriteProcess=HASH(0x556b408938c8)) called at /usr/lib/os-autoinst/backend/driver.pm line 72
    backend::driver::start(backend::driver=HASH(0x556b40a88648)) called at /usr/lib/os-autoinst/backend/driver.pm line 37
    backend::driver::new("backend::driver", "s390x") called at /usr/lib/os-autoinst/OpenQA/Isotovideo/Backend.pm line 14
    OpenQA::Isotovideo::Backend::new("OpenQA::Isotovideo::Backend") called at /usr/lib/os-autoinst/OpenQA/Isotovideo/Runner.pm line 100
    OpenQA::Isotovideo::Runner::create_backend(OpenQA::Isotovideo::Runner=HASH(0x556b3b1b8a38)) called at /usr/bin/isotovideo line 134

openQA test in scenario opensuse-Tumbleweed-DVD-s390x-autoyast_zvm@s390x-zVM-vswitch-l2 fails in
bootloader_start

Has been there any openQA changes during the Christmas time, what can have an effect on the boot process for s390x?

Test suite description¶

Create HDD for s390x textmode

Reproducible¶

Fails since (at least) Build 20231228

Expected result¶

Last good: 20231115 (or more recent)

Suggestions¶

• See related ticket #137408 about the recent o3 setup
• Confirm what s390zl11.openqanet.opensuse.org is and where it should be reachable from
  • Check the worker config
  • Lookup ipmi config? There is no ipmi
  • Check if there's an entry in pillars / Add a new entry
• Verify if this is a regression or a product issue
• Optional: Try to login to the machine manually with x3270, same as openQA tests do
• Read https://progress.opensuse.org/projects/openqav3/wiki/#o3-s390-workers about the setup
• Ask Oliver for details about the worker, since he might have been the last to work on it (if he still remembers), and mgriessmeier and nicksinger
• Ask Ada

Further details¶

Always latest result in this scenario: latest