Actions
action #50456
closed[functional][u] gather logs and information from SUT in failed state
Status:
Resolved
Priority:
High
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 25
Start date:
2019-04-16
Due date:
% Done:
0%
Estimated time:
Difficulty:
hard
Description
Motivation¶
As discussed in https://progress.opensuse.org/issues/49763 a way to gather logs from a SUT in failed state (e.g. according to bsc#1130701) would be very useful
Some good entry points are provided in the related ticket
Acceptance criteria¶
- AC1 Kernel messages do not cause pot_fail_hook to fail
- AC2 When bsc#1130701 happens, the job provides logs from post_fail_hook.
- AC3 A proper console is used for kernel messages (e.g. log-console on tty5)
Suggestions¶
- Find out why on aarch64 the behavior of the serial and root console is different (merged output)
- Implement a solution to avoid that kernel messages interrupt the uploading of logs.
- We could use another console to upload logs. There is a console log-console on tty5
Checklist
- Investigate why kernel messages are sent to root-console only on aarch64
- Don't send kernel messages to root-console or don't use root-console
Actions