action #32683
closed[sle][functional][u][medium] Implement proper post_fail_hook for boot_to_desktop
0%
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
Updated by okurz almost 7 years ago
- Description updated (diff)
- Status changed from New to Workable
Updated by okurz almost 7 years ago
- Due date changed from 2018-04-10 to 2018-05-08
not enough capacity in S14, moving
Updated by okurz almost 7 years ago
- Related to action #34609: [sle][functional][u][medium] Improve Implementation of workaround for bsc#1083646 and debug output in reconnect_s390 on S390-KVM added
Updated by okurz over 6 years ago
- Blocked by action #33202: [sle][functional][s390x][zkvm][u][hard] test fails in boot_to_desktop - still insufficient error reporting, black screen with mouse cursor - we all hate it (was: I hate it) added
Updated by okurz over 6 years ago
- Subject changed from [sle][functional][u] Implement proper post_fail_hook for boot_to_desktop to [sle][functional][u][medium] Implement proper post_fail_hook for boot_to_desktop
- Description updated (diff)
- Due date changed from 2018-05-08 to 2018-06-05
- Target version changed from Milestone 15 to Milestone 16
Let's try to do it after #33202
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-06-05 to 2018-07-03
- Status changed from Workable to Blocked
- Assignee set to mgriessmeier
- Target version changed from Milestone 16 to Milestone 17
Updated by okurz over 6 years ago
- Target version changed from Milestone 17 to Milestone 17
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-07-03 to 2018-07-17
Updated by okurz over 6 years ago
- Due date deleted (
2018-07-17) - Target version changed from Milestone 17 to Milestone 21+
Updated by mgriessmeier about 6 years ago
- Status changed from Blocked to Workable
- Assignee deleted (
mgriessmeier)
blocker seems to be resolved
Updated by okurz about 6 years ago
- Related to action #43376: [functional][u] Adapt opensusebasetest to provide dmesg and journal log added
Updated by okurz about 6 years ago
- Blocks action #42863: [sle][functional][u] test fails in first_boot - hard to see what is exactly the cause for timeout issue added
Updated by jorauch about 6 years ago
- Status changed from Workable to In Progress
- Assignee set to jorauch
Updated by jorauch about 6 years ago
- Status changed from In Progress to Feedback
PR open for discussion:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6370
Updated by okurz about 6 years ago
- Target version changed from Milestone 21+ to Milestone 21
Updated by jorauch about 6 years ago
Finally working:
http://pinky.arch.suse.de/tests/1685#step/boot_to_desktop/4
Oops wrong ticket, please ignore
Updated by okurz about 6 years ago
- Priority changed from Normal to High
- Target version changed from Milestone 21 to Milestone 22
Updated by mgriessmeier almost 6 years ago
reasoning for bumping this to urgent?
Updated by okurz almost 6 years ago
"Urgent" now because it is a "High" ticket hanging around for a month.
Updated by jorauch almost 6 years ago
Something that lies around for ages cannot be urgent in my opinion.
Nevertheless I updated the PR again and since no better ideas came up so far, we could at least merge the basic version
Updated by jorauch almost 6 years ago
- Status changed from Feedback to Workable
As agreed with okurz we should extract the methodics of the PFH to some sort of common boot-basetest to avoid duplication in between the boot tests
Updated by jorauch almost 6 years ago
- Status changed from Workable to Feedback
PR is updated according the agreement, I suggest merging and then finetune it as soon as we get ideas how to improve it
Updated by okurz almost 6 years ago
- Has duplicate action #44345: [functional][u] test fails in first_boot - Implement workaround to try to login instead of just pressing escape and hoping for the best added
Updated by okurz almost 6 years ago
- Target version changed from Milestone 22 to Milestone 23
Updated by jorauch almost 6 years ago
- Status changed from Feedback to Resolved
PR merged and did not break production, considering it as done