action #96287
closed
Added by hurhaj almost 3 years ago.
Updated over 2 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP3-Online-QR-x86_64-lvm+RAID1@svirt-hyperv2016-uefi fails in
setup_libyui
Test suite description¶
Maintainer: slindomansilla, jrauch
Combination of LVM and RAID1, installation of RAID1 on top of LVM using expert partitioner.
(crypt-)LVM installations can take longer, especially on non-x86_64 architectures.
Reproducible¶
Fails since (at least) Build 188.11
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
- Parent task set to #96302
Setting to parent task to have a common tracker
- Status changed from New to Feedback
So, this failure on setup_libyu is not something affected by test code changes. Also it was noticed on hyperv during regular builds. Hyper-v tests are not stable quite often and sporadically fail. Restart fixed that.
But the test suite failed further on setup_raid1_lvm and this is happened due to wrong schedule (non-UEFI, but the system is UEFI). Fixed in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13005
- Status changed from Feedback to Resolved
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm+RAID1@svirt-hyperv2016-uefi
https://openqa.suse.de/tests/6872300
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 label in the openQA scenario is removed
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm+RAID1@svirt-hyperv2016-uefi
https://openqa.suse.de/tests/7059809
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 label in the openQA scenario is removed
Also available in: Atom
PDF