action #32689
closed
[sle][functional][fast][u] test fails in boot_to_desktop: Unable to switch from login_shell to gnome session
Added by mgriessmeier about 6 years ago.
Updated about 6 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-x86_64-yast2_ncurses@64bit fails in
boot_to_desktop
Hypothesis¶
- H1: somehow the gnome image got overwritten with a non-gnome image
- H2: starting gnome takes longer than our timeout
Reproducible¶
Fails since (at least) Build 288.8
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
- Related to action #32677: [sle][functional][u][svirt-xen][medium] gnome@svirt-xen, currently test fails in shutdown: Could not switch to gnome session added
- Related to action #32440: [sle][functional][u][easy] Change PUBLISH_HDD_1 of skip_registration test suite to be MACHINE aware added
#32440 is on H1 ("overwriting images").
- Priority changed from Normal to High
Increasing priority as blocks tests
- Status changed from New to In Progress
- Assignee set to mloviska
Images should not be overwritten any more due to diverse values PUBLISH_HDD_1 variable in create_hdd_gnome and create_hdd_textmode test suites.
PUBLISH_HDD:¶
- create_hdd_gnome -> PUBLISH_HDD_1=SLES-%VERSION%-%ARCH%-Build%BUILD%@%MACHINE%-gnome.qcow2
- create_hdd_textmode -> PUBLISH_HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%.qcow2
- Status changed from In Progress to Resolved
mloviska wrote:
Images should not be overwritten any more due to diverse values PUBLISH_HDD_1 variable in create_hdd_gnome and create_hdd_textmode test suites.
PUBLISH_HDD:¶
- create_hdd_gnome -> PUBLISH_HDD_1=SLES-%VERSION%-%ARCH%-Build%BUILD%@%MACHINE%-gnome.qcow2
- create_hdd_textmode -> PUBLISH_HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%.qcow2
Did you check all jobs which use HDD_1 and change values there as well?
btw, I've triggered 30 jobs yesterday and had this issue once in those 30 runs
I did, but ofc I could miss something among that pile of test suits. I will double check, thanks!
@mgriessmeier could you please share the problematic test suite name ?
Also available in: Atom
PDF