action #68761
open[qe-core] HyperV reboot unstable
0%
Description
Rebooting a HyperV worker results often (but not always) in Stall Detected, e.g. in https://openqa.suse.de/tests/4427647/modules/journalctl/steps/40.
openQA fails to detect the grub2 screen. While observing a failing run I noticed, that the images freezes for some time and gets restored at the login screen, without showing GRUB2 or the boot messages. It looks like the vnc needs to reconnect after a certain timeout and misses the grub2 screen.
A dedicated triple-reboot test for this issue on HyperV fails: https://openqa.suse.de/tests/4428045. The test "reboot" does nothing more than reboot three times.
use base "consoletest";
use strict;
use warnings;
use testapi;
use utils;
use version_utils;
use power_action_utils 'power_action';
sub reboot {
my ($self) = @_;
power_action('reboot', textmode => 1);
$self->wait_boot(bootloader_time => 200);
select_console 'root-console';
}
sub run {
my ($self) = @_;
$self->select_serial_terminal;
reboot($self);
reboot($self);
reboot($self);
}
1;
Updated by SLindoMansilla over 4 years ago
- Subject changed from HyperV reboot unstable to [u] HyperV reboot unstable
Updated by SLindoMansilla over 4 years ago
- Blocked by action #35038: [qe-core][sle][functional][hyperv] extra tests on hyperv added
Updated by szarate over 4 years ago
This is being hit by stall detection, a quick try could be by modifying line the assert_screen inside wait_boot (like 614?) to also look for any console, and act accordingly with a record_info("Grub skipped", "Host took too long to check screen", result => "fail");
so that the test keeps going, and is not marked as failed, due to grub being skipped, but the box is colored to reflect what happened.
However, atm hyperV is a bit of in low prio, but the rework could be generic though.
Updated by tjyrinki_suse over 4 years ago
- Subject changed from [u] HyperV reboot unstable to [qe-core] HyperV reboot unstable
Updated by mgrifalconi 5 days ago
- Status changed from New to Feedback
wouldn't this be for virtualization team?