action #99261

[sporadic] s390x tests fail in first_boot and boot_to_desktop

Added by syrianidou_sofia about 1 month ago. Updated 17 days ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


This failure has occurred both for first_boot and boot_to_desktop on s390x. What happens is that handle_login function in lib/ is checking if the desktop matches with gnome-activities and then presses esc.

249     if (match_has_tag('gnome-activities')) {
250         send_key('esc');
251         assert_screen([qw(generic-desktop opensuse-welcome)]);
252     }

After that it expects that the desktop will match with normal generic desktop, but we see no change. According to the autoinst.log the esc key is sent indeed. We need to check why the key takes no effect on the desktop. An idea would be to add a second check, for example: send_key('esc') if assert_screen "gnome-activities"; so that in case 'esc' is not accepted the first time, it would take effect, the second time.


openQA test in scenario sle-15-SP4-Online-s390x-zfcp@s390x-zfcp fails in

Test suite description

Testsuite maintained at Maintainer: QE Yast, mgriessmeier

Installation-only test configuring an s390x ZFCP storage.


Fails since (at least) Build 29.1

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest


#1 Updated by syrianidou_sofia about 1 month ago

  • Project changed from openQA Tests to qe-yast
  • Description updated (diff)
  • Category deleted (Bugs in existing tests)
  • Target version set to Current

#2 Updated by syrianidou_sofia about 1 month ago

  • Description updated (diff)

#3 Updated by openqa_review 17 days ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: btrfs_libstorage-ng@s390x-kvm-sle15

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Also available in: Atom PDF