Project

General

Profile

Actions

action #51770

closed

[functional][u] 'sysrq: Show Blocked State' pollutes console and assert_screen fails

Added by ggardet_arm almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 25
Start date:
2019-05-21
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

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

Further details

Always latest result in this scenario: latest

Copied from #50456

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

  • 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.

Related issues 1 (0 open1 closed)

Related to openQA Tests - action #50456: [functional][u] gather logs and information from SUT in failed stateResolvedzluo2019-04-16

Actions
Actions

Also available in: Atom PDF