action #99603
svirt-xen-hvm jobs entering emergency mode in first boot
0%
Description
Observation¶
openQA test in scenario sle-15-SP4-Online-x86_64-xfs@svirt-xen-hvm fails in
first_boot
also fails on textmode and minimal+base_yast
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: QE Yast, QE Kernel
Installation test with explicit selection of "xfs" instead of default.
Reproducible¶
Fails since (at least) Build 43.1 (current job)
Expected result¶
Last good: 39.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
History
#1
Updated by JERiveraMoya over 1 year ago
Updated by - Tags deleted (
qe-yast-refinement) - Project changed from qe-yam to openQA Infrastructure
- Subject changed from Investigate failure in first_boot on svirt-xen-hvm to svirt-xen-hvm jobs entering emergency mode in first boot
- Target version deleted (
Current)
In latest build we have entering in emergency mode:
https://openqa.suse.de/tests/7386046#step/first_boot/8
https://openqa.suse.de/tests/7370543#step/first_boot/8
https://openqa.suse.de/tests/7369516#step/first_boot/8
#2
Updated by okurz over 1 year ago
Updated by - Project changed from openQA Infrastructure to qe-yam
- Priority changed from Normal to Urgent
mloviska mentioned https://bugzilla.suse.com/show_bug.cgi?id=1190930 as related.
https://openqa.suse.de/tests/7262467#comment-389914 shows a pretty clear picture to me:
- xfs:investigate:retry: https://openqa.suse.de/t7264489 failed -> reproducible
- xfs:investigate:last_good_tests:53ac4135c43280e0f44a7ed02d4f33680c4c8f5d: https://openqa.suse.de/t7264492 failed -> no test regression
- xfs:investigate:last_good_build:39.1: https://openqa.suse.de/t7264495 passed -> no infrastructure or backend problems
- xfs:investigate:last_good_tests_and_build:53ac4135c43280e0f44a7ed02d4f33680c4c8f5d+39.1: https://openqa.suse.de/t7264497 passed -> no infrastructure or backend problems
@qe-yast please make sure there is a proper bug report that is also correctly marked as blocker. https://bugzilla.suse.com/show_bug.cgi?id=1190930 could be it but does not yet have the "Blocker" flag yet.
#3
Updated by JERiveraMoya over 1 year ago
- Status changed from New to Rejected
Rejected, see https://bugzilla.suse.com/show_bug.cgi?id=1190930