action #123571
open[xen][virtualization] test fails in bootloader_start - xen domains fail to startup with unclear error messages
0%
Description
Observation¶
See one example
openQA test in scenario sle-15-SP5-Online-x86_64-guided_ext4@svirt-xen-hvm fails in
bootloader_start
but there are multiple more, e.g. see
https://openqa.suse.de/tests/overview?machine=svirt-xen-pv&modules=bootloader_start&modules_result=failed&version=15-SP5
8 jobs failed in the same step at time of writing
Reproducible¶
Fails since (at least) Build 64.1, maybe related to the move of the machine openqaw5-xen.qa.suse.de from NUE-2.2.14 to NUE-SRV2, see #123028 for details.
Expected result¶
Last good: 61.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz over 2 years ago
- Priority changed from High to Urgent
As we discussed in the weekly qam-qasle-collaboration project: https://openqa.suse.de/tests/overview?result=none&result=failed&result=incomplete&result=skipped&result=obsoleted&result=parallel_failed&result=parallel_restarted&result=user_cancelled&result=user_restarted&result=timeout_exceeded&arch=&flavor=JeOS-for-kvm-and-xen-Updates&machine=&test=&modules=&module_re=&build=20230124-1&distri=sle&groupid=419&version=15-SP3# shows mostly "bootloader_svirt" failing but no ticket linked. Same issue?
@jlausuch is this one of the example you had in mind regarding openqaw5-xen?
Updated by jlausuch over 2 years ago
- Priority changed from Urgent to High
okurz wrote:
@jlausuch is this one of the example you had in mind regarding openqaw5-xen?
Yes, we were using https://progress.opensuse.org/issues/123028 for some jobs in SP4, but not all of the aggregates failing tests are labelled.
Updated by openqa_review about 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: msdos@svirt-xen-pv
https://openqa.suse.de/tests/10525400#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 slo-gin about 1 year ago
This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin about 1 hour ago
- Priority changed from Normal to Low
This ticket was set to Normal priority but was not updated within the SLO period. The ticket will be set to the next lower priority Low.