action #68359
open[opensuse] QEMU cannot boot from HDD on some chained tests (create_hdd_gnome-wayland -> desktopapps-other-wayland, etc.)
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-desktopapps-other-wayland@aarch64 fails in
boot_to_desktop
QEMU cannot boot from HDD on some chained tests. For example, tests started after create_hdd_gnome-wayland
:
-
desktopapps-other-wayland
: https://openqa.opensuse.org/tests/1311998 -
desktopapps-gnome-wayland
: https://openqa.opensuse.org/tests/1312068 -
desktopapps-documentation-wayland
: https://openqa.opensuse.org/tests/1312082
Whereas a similar test run successfully: create_hdd_textmode
=> extra_tests_ai_ml
: https://openqa.opensuse.org/tests/1312064
Test suite description¶
Reproducible¶
Fails since (at least) Build 20200622 (current job)
Expected result¶
Last good: 20200621 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by ggardet_arm almost 5 years ago
The command file
returns data
instead of QEMU QCOW2 Image (v3), XXX bytes
on the broken file.
Updated by ggardet_arm almost 5 years ago
On the same worker (openqa-aarch64
):
-
create_hdd_textmode
create_hdd_gnome
create_hdd_gnome-x11
are ok -
create_hdd_gnome-wayland
create_hdd_kde
are broken
Updated by ggardet_arm almost 5 years ago
- Priority changed from High to Normal
There was nothing obvious in dmesg
, and SDD smart info were good.
As a workaround, I restarted the initial test to recreate the QCOW2 image.
Updated by SLindoMansilla almost 5 years ago
- Subject changed from QEMU cannot boot from HDD on some chained tests (create_hdd_gnome-wayland -> desktopapps-other-wayland, etc.) to [opensuse] QEMU cannot boot from HDD on some chained tests (create_hdd_gnome-wayland -> desktopapps-other-wayland, etc.)
Updated by okurz over 3 years ago
This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period). This update was done as agreed within the SUSE QE Sync call 2021-09-01
Updated by slo-gin over 2 years ago
This ticket was set to Normal 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 year ago
This ticket was set to Normal 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 2 months 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.