action #51770
Updated by szarate almost 5 years ago
## Observation `clamav` test fails and `sysrq: Show Blocked State` pollutes the console and `assert_screen` fails, so no logs are uploaded. ## Acceptance criteria - **AC1:** The logs are uploaded to the webui. - **AC2:** The log-console is used in the post_fail_hook ## Reproducible - In scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-extra@aarch64-HD24G - Fails since Build [20190520](https://openqa.opensuse.org/tests/938978/modules/clamav/steps/33) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?test=jeos-extra&machine=aarch64-HD24G&distri=opensuse&arch=aarch64&flavor=JeOS-for-AArch64&version=Tumbleweed) # Copied from #50456 ## Acceptance criteria - **AC1** Kernel messages do not cause pot_fail_hook to fail - **AC2** When [bsc#1130701](https://bugzilla.suse.com/show_bug.cgi?id=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 - **An easier suggestion is to simply press enter after the sysrq is called.** - Ensure that the sysrq thing is called in a different console, or that a clear is called after the sysrq information is shown - 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](https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/susedistribution.pm#L406)