action #174751
closed[qe-core] test fails in mdadm
100%
Description
Observation¶
This test fails quite frequently and often requires multiple re-triggers to pass successfully. This becomes particularly cumbersome as the full test plan takes nearly 2 hours to complete.
Would it be possible to review this test and work on making it more robust? This would save quite a lot test machine time.
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_textmode@64bit fails in
mdadm
Test suite description¶
Maintainer: slindomansilla@suse.de.
Mainly post-installation console extra tests.
Reproducible¶
Fails since (at least) Build 20240702
Expected result¶
Last good: 20240611 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by openqa_review 2 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_textmode
https://openqa.opensuse.org/tests/4754404#step/mdadm/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 openqa_review about 2 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_textmode
https://openqa.opensuse.org/tests/4802028#step/mdadm/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 szarate 5 days ago ยท Edited
Looking at the failure, seems the script is doing something off that ends up in the consistent failure we're seeing
To optimalize recovery speed, it is recommended to enable write-indent bitmap, do you want to enable it now? [y/N]? mdadm: bad option.
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
Continue creating array [y/N]? mdadm: bad option.
mdadm: create aborted.
# cat /proc/mdstat
Personalities : [raid0]
unused devices: <none>
Expected pattern "active raid1" not found!
Updated by mgrifalconi 5 days ago
- Tags set to bugbusters
- Subject changed from test fails in mdadm to [qe-core] test fails in mdadm
- Target version set to QE-Core: Ready
Same error in 15SP7 latest build https://openqa.suse.de/tests/17000877#step/mdadm/18