[opensuse][kde] test fails in await_install - timeout not working properly
openQA test in scenario opensuse-Tumbleweed-KDE-Live-x86_64-kde_live_upgrade_leap_42.3@64bit-2G fails in
The underlying issue is probably a missed 'reboot_now' screen, and the system has already rebooted. Though, the same would happen if the live install were stuck.
For live installs, the timeout is no more checked after the first lock screen, as it just wiggles the mouse and repeats the loop.
Test suite description¶
Uses the live installer on the kde live media for upgrading the system.
Fails since (at least) Build 20190625 (current job)
Last good: 20190624 (or more recent)
Always latest result in this scenario: latest
#1 Updated by okurz over 3 years ago
- Status changed from New to In Progress
- Assignee set to StefanBruens
seems like you are adressing this on your own :) -> https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7756
#2 Updated by SLindoMansilla over 3 years ago
- Subject changed from test fails in await_install - timeout not working properly to [opensuse][kde] test fails in await_install - timeout not working properly
As a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).
Please, feel free to adjust the category or the "[label]" if you think different.
#6 Updated by okurz about 3 years ago
- Status changed from In Progress to Feedback
Hi StefanBruens, it does not look like you are still working on this? I can see that the failing scenario fails now in https://openqa.opensuse.org/tests/1068929#step/disable_grub_timeout/14 . I reported a bug https://bugzilla.opensuse.org/show_bug.cgi?id=1155515 and labeled the failing scenario accordingly. Also I realized that due to https://github.com/yast/yast-installation/blob/master/src/lib/installation/clients/inst_finish.rb#L153 the installer should actually have no timeout for reboot in "live installation" mode anyway. I reported https://bugzilla.opensuse.org/show_bug.cgi?id=1155516 for this. For the handling in test you might want to close your ticket in favor of #50615 ?
#9 Updated by okurz almost 3 years ago
- Status changed from Blocked to Resolved
- Target version changed from Current Sprint to Done