Project

General

Profile

Actions

action #115118

closed

[qe-core] test fails in bootloader_start: redcurrant is down - trigger a job failure when an lpar is not available

Added by szarate over 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2022-08-08
Due date:
% Done:

100%

Estimated time:
3.00 h
Difficulty:
Sprint:
QE-Core: August Sprint (Aug 03 - Aug 31)

Description

Hi, it looks like the powerVM worker is down, please help to take a look at it, thanks.

When looking at the screen, we can clearly see that the lpar shows that it's unavailable, we should be able to recognize this, and fail the job, as there's no need to continue further.

Suggestions:

Use check_screen to look for the "unavailable" message, from the lpar information, and fail the job if it's found.

Acceptance Criteria:

  • AC1: Job fails when lpar is unavailable
  • AC2: Error message is shown stating the reason, no further action is taken by openQA.

Observation

openQA test in scenario sle-15-SP4-Full-ppc64le-sles+sdk+proxy_SCC_via_YaST_ncurses_test@ppc64le-hmc-single-disk fails in
bootloader_start

Test suite description

Add add-on via SCC using YaST module in ncurses.

Reproducible

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

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Copied from openQA Infrastructure - action #115094: [tools] test fails in bootloader_start: redcurrant is down size:MResolvednicksinger2022-08-08

Actions
Actions

Also available in: Atom PDF