action #18996
closedtest fails in setup_zdup (all zdup tests apparently)
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-13.1-gnome@64bit fails in
setup_zdup
Reproducible¶
Fails since (at least) Build 20170505
Expected result¶
Last good: 20170504 (or more recent)
Further details¶
Always latest result in this scenario: latest
More observations¶
Since today, all zdup tests seem to fail switching to the console. I also restarted a Leap 42.3 test that worked yesterday: today it fails the same way as every TW zdup test (https://openqa.opensuse.org/tests/399229). As this is booting an old disk image even before any 'product' specific code to be tested is running, this must be a change on the openQA infra causing this.
Updated by okurz about 8 years ago
- Related to coordination #18964: [functional][epic][u]Bootloader/boot functions refactor added
Updated by okurz about 8 years ago
- Status changed from New to In Progress
- Assignee set to okurz
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2774#discussion_r114492238 caused the problem for openSUSE because for openSUSE we commonly have auto-login so that assert_screen 'displaymanager' does not apply here.
Updated by okurz about 8 years ago
- Status changed from In Progress to Feedback
See https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2849 as a "quick-fix" and https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2850 as a proper way by simply reverting the "wait_boot" call in setup_zdup.
Updated by okurz about 8 years ago
- Status changed from Feedback to Resolved