action #13896
closedcollect linuxrc logs on installation startup problems / turn off plymouth to debug startup problems
0%
Description
See bsc#999231 for motivation.
If we have a test stuck at https://openqa.suse.de/tests/590222#step/welcome/10 we need debug logs for the developers.
ideas¶
- collect linuxrc logs
- turn of plymouth to debug startup problems
Updated by maritawerner over 7 years ago
- Related to action #14068: [tools] Gather more system information and logs in case of boot/reboot times out added
Updated by szarate over 7 years ago
as suggested by Oliver, a post_fail_hook call would be very useful, and may be a memory dump (but in this kind of cases, i don't see that its really necessary.
One suggestion would be that for similar cases, if the machine is still usable, not only press esc, but also collect dmesg and other logs.
Updated by okurz over 7 years ago
szarate wrote:
One suggestion would be that for similar cases, if the machine is still usable, not only press esc, but also collect dmesg and other logs.
we have this part already, see
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/first_boot.pm#L92
The issue here is about the installation system failing to boot, not the installed system.
Updated by okurz over 7 years ago
- Status changed from New to In Progress
- Assignee set to okurz
Updated by okurz over 7 years ago
- Status changed from In Progress to Resolved
Updated by okurz over 7 years ago
- Status changed from Resolved to In Progress
I should check if we still need the workaround as in https://openqa.suse.de/tests/714329#step/bootloader_uefi/6 or if the last PR replaces that.
Updated by okurz over 7 years ago
Updated by okurz over 7 years ago
- Status changed from In Progress to Resolved
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2310 merged so we are good