QA » openQA Project » openQA Tests

As mentioned in #139112#note-13, the process is slow and at least TIMEOUT_SCALE=4 was needed in the original verification job. The failed job in this ticket has TIMEOUT_SCALE=3 which seems to be insufficient.

I tried to set TIMEOUT_SCALE=4 it cannot work: https://openqa.suse.de/tests/13818599#step/bootloader_start/24
I extend the time ' assert_screen "pvm-grub-command-line-fresh-prompt", 1800, no_wait => 1;' at lib/bootloader_pvm.pm file.
Failed job: https://openqa.suse.de/tests/13825504

This ticket was set to Urgent 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.

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: ha_migration_online_pscc_sles15sp5_pre
https://openqa.suse.de/tests/13959153#step/bootloader/1

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
3. 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.