action #115118
closed[qe-core] test fails in bootloader_start: redcurrant is down - trigger a job failure when an lpar is not available
100%
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
Updated by szarate over 2 years ago
- Copied from action #115094: [tools] test fails in bootloader_start: redcurrant is down size:M added
Updated by rfan1 over 2 years 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.
Updated by rfan1 over 2 years ago
- Status changed from Workable to In Progress
- % Done changed from 0 to 20
Updated by rfan1 over 2 years ago
- % Done changed from 20 to 70
Updated by rfan1 over 2 years ago
- Status changed from In Progress to Feedback
- % Done changed from 70 to 90
PR merged
Updated by bschmidt about 2 years ago
just like for redcurrant this is the same for nessberry https://openqa.suse.de/tests/9378054#step/bootloader_start/7
Thanks, then I can verify that the issue can be captured now.
Updated by rfan1 about 2 years ago
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100
Updated by openqa_review about 2 years 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
https://openqa.suse.de/tests/9416774#step/bootloader_start/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by okurz about 2 years ago
- Related to coordination #117268: [epic] Handle reduced PowerPC ressources added
Updated by okurz about 2 years ago
- Related to deleted (coordination #117268: [epic] Handle reduced PowerPC ressources)
Updated by openqa_review about 2 years ago
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
https://openqa.suse.de/tests/9563852#step/bootloader_start/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.