action #115118

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

Added by szarate about 2 months ago. Updated 19 days ago.

Bugs in existing tests
Target version:
Start date:
Due date:
% Done:


Estimated time:
3.00 h


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.


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.


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

Test suite description

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


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

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


#1 Updated by szarate about 2 months ago

  • Copied from action #115094: [tools] test fails in bootloader_start: redcurrant is down size:M added

#2 Updated by rfan1 about 2 months ago

  • Assignee set to rfan1
  • Estimated time set to 3.00 h

Plan to add a new needle there to fail the test if lpar is not in right status.

#3 Updated by rfan1 about 2 months ago

  • Status changed from Workable to In Progress
  • % Done changed from 0 to 20

#5 Updated by rfan1 about 2 months ago

  • Status changed from In Progress to Feedback
  • % Done changed from 70 to 90

PR merged

#6 Updated by bschmidt about 1 month ago

just like for redcurrant this is the same for nessberry

Thanks, then I can verify that the issue can be captured now.

#7 Updated by rfan1 about 1 month ago

  • Status changed from Feedback to Resolved
  • % Done changed from 90 to 100

#8 Updated by openqa_review 19 days ago

  • Status changed from Resolved to Feedback

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: SAPHanaSR_ScaleUp_PerfOpt_node02@ppc64le-hmc-sap

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Also available in: Atom PDF