action #77077: test fails in first_boot, no logs are collected from emergency shell - qe-yam - openSUSE Project Management Tool

Actions

Copy link

action #77077

closed

test fails in first_boot, no logs are collected from emergency shell

Added by JRivrain over 3 years ago. Updated over 3 years ago.

Status:

Resolved

Priority:

High

Assignee:

syrianidou_sofia

Target version:

SUSE QA - SLE 15 SP3

Start date:

2020-11-06

Due date:

% Done:

Estimated time:

Description

Observation¶

When this type of failure happens we cannot always report a bug here as we may have no clue at all what is going on, example here: https://openqa.suse.de/tests/4863653#.

There are four problems:

1 - We do not wait long enough for the emergency shell
2 - It is sporadic. From my observations, happens once every 15 runs approximately, so it's really hard to reproduce manually
3 - If we try to increase the time needed, a I did here: http://waaa-amazing.suse.cz/tests/13313#step/first_boot/2 then the password does not get entered, or at least not reliably.
4 - We should try to get more logs than what is currently collected, to facilitate the bug report.

openQA test in scenario sle-15-SP3-Online-x86_64-RAID0@64bit fails in
first_boot

Acceptance criteria¶

Logging to emergency shell works stably
Redirect basic logs to serial port, like dmesg, journalctl, fstab, rdosreport, etc.

Test suite description¶

Maintainer: slindomansilla, jrauch

Installation of RAID0 using expert partitioner

Reproducible¶

Fails since (at least) Build 63.1 (current job)

Expected result¶

Last good: 44.1 (or more recent)

Further details¶

Always latest result in this scenario: latest

Actions

Copy link

Updated by JRivrain over 3 years ago

Project changed from openQA Tests to qe-yam
Category deleted (~~Bugs in existing tests~~)

Actions

Copy link

Updated by JRivrain over 3 years ago

Description updated (diff)
Priority changed from Urgent to High

Changed description and decreased severity as in the case I reported in initially I could find a bit of useful logs, so I managed to report a bug: https://bugzilla.suse.com/show_bug.cgi?id=1178515. Probably the same issue as with raid0 test suite, as this also creates a raid0.
In he raid0 test suite's failure there is no useful log at all.

Actions

Copy link

Updated by riafarov over 3 years ago

Subject changed from test fails in first_boot to test fails in first_boot, no logs are collected from emergency shell
Description updated (diff)
Status changed from New to Workable
Target version set to SLE 15 SP3