Project

General

Profile

Actions

action #43376

closed

[functional][u] Adapt opensusebasetest to provide dmesg and journal log

Added by szarate over 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Category:
Enhancement to existing tests
Target version:
Start date:
2018-11-05
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP4-Server-DVD-ppc64le-default@ppc64le fails in
keymap_or_locale

Has a test (keymap_or_locale) failing, that inherits from opensusebasetest, however while looking at the asset list, there's no dmesg, or journal log, making a bug report kernel related, basically useless (IMO), however system_prepare (https://openqa.suse.de/tests/2234331#step/system_prepare/3) inherits from consoletest, and properly saves the journal file.

I guess it would be possible to harmonize them?

Acceptance criteria

  • AC1: whenever keymap_or_locale fails dmesg and journal log are available

Related issues 5 (0 open5 closed)

Related to openQA Tests - action #36126: [functional][u] post_fail_hook matches on "text_login_root" before actual tty switch and therefore never logs inResolvedzluo2018-05-14

Actions
Related to openQA Tests - action #42038: [sle][functional[u] test fails in shutdown - add post_fail_hook for shutdown module if possibleResolvedzluo2018-10-05

Actions
Related to openQA Tests - action #32683: [sle][functional][u][medium] Implement proper post_fail_hook for boot_to_desktopResolvedjorauch2018-03-02

Actions
Related to openQA Tests - action #41237: [functional][u][ipmi] test fails in first_boot after system shows text tty login prompt but fails to connect to machine over SSH -> need better post_fail_hook or retry, compare to s390x approachRejectedSLindoMansilla2018-09-19

Actions
Blocked by openQA Tests - action #35877: [functional][u] Find out in post-fail-hook if system is I/O-busyResolvedzluo2018-05-03

Actions
Actions

Also available in: Atom PDF