action #166892
closed
Added by ph03nix 9 months ago.
Updated about 1 month ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-micro-5.5-DVD-Updates-aarch64-slem_installation_docker@aarch64 fails in
disk_boot
Test suite description¶
Reproducible¶
Fails since (at least) Build 20240916-1
Expected result¶
Last good: 20240915-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
The issue is only present on aarch64.
- Assignee changed from ph03nix to jlausuch
- Status changed from In Progress to Resolved
- Status changed from Resolved to In Progress
Ok, the reason for this new failure is not needle related. It's stuck in grub screen BECAUSE this is a custom HDD created in containers which disables grub timeout and I disabled the grub screen in ALL arch64 jobs in my PR.
Meanwhile, a conversation started about why we have different resolutions in the bootloader screen (sometimes 800x600, some other times 1024x768..
Related threads:
https://suse.slack.com/archives/C02CGKBCGT1/p1726729833801009 Old OVMF hardcodes 800x600, newer OVMF uses whatever QEMU specifies as preferred mode, which then depends on the QEMU version
https://suse.slack.com/archives/C02CANHLANP/p1726731665437149
- Status changed from In Progress to Resolved
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: slem_image_default@uefi-virtio-vga
https://openqa.suse.de/tests/15812246#step/disk_boot/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.
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.
- Priority changed from High to Normal
This ticket was set to High priority but was not updated within the SLO period. The ticket will be set to the next lower priority Normal.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF