action #126143
closedcoordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Try out different ipmi machine in Yam job group
0%
Description
There is an issue with current ipmi worker we used.
According to virtualization squad we could switch worker.
https://openqa.suse.de/tests/10694437
Acceptance criteria¶
AC1: Switch scenario to 64bit-ipmi-large-mem
Updated by JERiveraMoya over 1 year ago
- Project changed from openQA Tests to qe-yam
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Current
- Parent task set to #121876
Updated by JERiveraMoya over 1 year ago
- Subject changed from test fails in bootloader_start for ipmi woker to test fails in bootloader_start for ipmi worker
Updated by hjluo over 1 year ago
- Status changed from Workable to In Progress
- Assignee set to hjluo
Updated by hjluo over 1 year ago
Updated by hjluo over 1 year ago
now passed in 81.1 with grenache-1:16
https://openqa.suse.de/tests/10675807#settings
Updated by JERiveraMoya over 1 year ago
- Status changed from In Progress to Workable
- Assignee deleted (
hjluo) - Priority changed from Normal to Low
- Target version deleted (
Current)
Thanks for checking it.
Moving back to backlog, we might need this in future, I don't know how stable is to use that worker.
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_ker_mode_tests_crypt_web_intel_ipmi@64bit-ipmi
https://openqa.suse.de/tests/10954413#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 JERiveraMoya over 1 year ago
- Status changed from Workable to In Progress
- Assignee set to syrianidou_sofia
- Priority changed from Low to Normal
- Target version set to Current
Updated by JERiveraMoya over 1 year ago
@ssrianidou, could you please isos post?
we might be missing some param in https://openqa.suse.de/tests/11025375
perhaps once merged is a bit easier, otherwise we need to check settings for passing jobs with this worker.
Updated by JERiveraMoya over 1 year ago
- Subject changed from test fails in bootloader_start for ipmi worker to Try out different ipmi machine in Yam job group
Updated by syrianidou_sofia over 1 year ago
- Status changed from In Progress to Resolved
Under settings option MACHINE=64bit-ipmi-large-mem we have high failure rate due to pxeboot graphics problem: https://openqa.suse.de/tests/11051161#step/bootloader_start/8
on grenache-1:10 and some repository issue on grenache-1:17 : https://openqa.suse.de/tests/11043804#step/bootloader_start/10
Contacting the virtualization team here : https://suse.slack.com/archives/C02CGKV748P/p1683205911080479 didn't provide a solution, usable on osd.
There are two additional options for ipmi machine, 64bit-ipmi-nvdimm that exists only on grenache-1:11 which has a high success rate, so changing our test setting to MACHINE=virt-mm-64bit-ipmi would ensure that the test runs on worker grenache-1:11 but would probably take longer time to schedule. Another option is MACHINE=virt-mm-64bit-ipmi that exists in 8 workers and none seem to constantly fail.
VRs for virt-mm-64bit-ipmi:
https://openqa.suse.de/tests/11084215
https://openqa.suse.de/tests/11084202
https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/503