Actions
action #32683
closed[sle][functional][u][medium] Implement proper post_fail_hook for boot_to_desktop
Status:
Resolved
Priority:
Urgent
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA (private) - Milestone 23
Start date:
2018-03-02
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
Motivation¶
openQA test in scenario sle-15-Installer-DVD-x86_64-yast2_ncurses@64bit fails in
boot_to_desktop
We want to have proper possibilities to debug issues like this, so we'd need a proper post_fail_hook in boot_to_desktop
Acceptance criteria¶
- AC1: There is a post_fail_hook for boot_to_desktop at least trying to do anything, e.g. find out if the welcome message is there, exactly as for s390x, and logging the DISPLAY variables to crosscheck text-login vs. displaymanager/generic-desktop and nothing more!
Suggestions¶
- Read the current post_fail_hook for first_boot and boot_to_desktop (using a helper function wait_boot) and understand what it is doing
- Read the current bootup problems handling for s390x
- Apply something comparable for non-s390x backends
Further details¶
Always latest result in this scenario: latest
Actions