action #117700
open
- Project changed from openQA Tests (public) to qe-yam
- Category deleted (
Bugs in existing tests)
- Project changed from qe-yam to openQA Infrastructure (public)
- Related to action #117808: [qe-sap][y] Grub error: Timeout reading in bootloader on PowerVM added
- Project changed from openQA Infrastructure (public) to openQA Tests (public)
- Subject changed from openQA test fails in bootloader, bootloader_start to [qe-sap][y] openQA test fails in bootloader, bootloader_start
- Category set to Bugs in existing tests
This sounds very much related to #117808, same reasoning for assignment
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm+cancel_existing_cryptlvm@ppc64le-hmc-single-disk
https://openqa.suse.de/tests/9775466#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.
- Status changed from New to Rejected
This is a different issue, but also reflect the issue with network.
- Status changed from Rejected to New
- Subject changed from [qe-sap][y] openQA test fails in bootloader, bootloader_start to [qe-sap][y] Grub error: Stuck in "Welcome to Grub!" in PowerVM
- Subject changed from [qe-sap][y] Grub error: Stuck in "Welcome to Grub!" in PowerVM to [qe-sap][y] Grub error: Stuck in "Welcome to Grub!" on PowerVM
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: autoupgrade_sles15sp2_ltss_scc_basesys-srv-lp-tsm_def_full_ssh_auto_pre
https://openqa.suse.de/tests/10088398#step/bootloader/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 is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: offline_sles15sp2_ltss_media_basesys-srv_all_full_pre
https://openqa.suse.de/tests/10220104#step/bootloader/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 56 days if nothing changes in this ticket.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: RAID1@ppc64le-hmc-4disk
https://openqa.suse.de/tests/11076768#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 112 days if nothing changes in this ticket.
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.
Also available in: Atom
PDF