action #137192
open
[qe-sap] test fails in boot_windows - corrupted windows or qcow2 image?
Added by emiura 8 months ago.
Updated 4 months ago.
Category:
Bugs in existing tests
Description
Seems like the qcow2 or the windows image got corrupted and it is preventing it to boot (first saw it happening on 15SP5QU RC1)
Observation¶
openQA test in scenario sle-15-SP5-Online-QR-SAP-ppc64le-sles4sap_remote_desktop_windows_client_ppc64le@64bit-2gbram fails in
boot_windows
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build 115.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: sles4sap_remote_desktop_windows_client_ppc64le@64bit-2gbram
https://openqa.suse.de/tests/12230624#step/boot_windows/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.
- Subject changed from test fails in boot_windows - corrupted windows or qcow2 image? to [qe-sap] test fails in boot_windows - corrupted windows or qcow2 image?
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: sles4sap_remote_desktop_windows_client_ppc64le@64bit-2gbram
https://openqa.suse.de/tests/12399645#step/boot_windows/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.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: sles4sap_remote_desktop_windows_client_ppc64le@64bit-2gbram
https://openqa.suse.de/tests/13332429#step/boot_windows/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 56 days if nothing changes in this ticket.
Also available in: Atom
PDF