action #124430: Right key doesn't reach the SUT when switching to tab Bootloader Options - openQA Tests (public) - openSUSE Project Management Tool

However it seems like the problem is here:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/f09658ba40775c5d1a413e64f4e2dca2df1b2f53/tests/installation/disable_grub_timeout.pm#L56
The test is supposed to press "Tab" until it reaches the needle, but is somehow stuck on "Kernel parameters" tab.
I am wondering if this is an actual product bug and yast is unresponsive for some reason.

Actions

Copy link

Updated by JERiveraMoya almost 2 years ago

Status changed from New to Rejected

it was a mistake that we didn't use libyui-rest-api here.
Please do not label with this ticket.

Actions

Copy link

Updated by tjyrinki_suse almost 2 years ago

What happens next with the disable_grub_timeout problems preventing 15-SP5 testing? Is there another ticket or a fix upcoming?

Actions

Copy link

Updated by acarvajal almost 2 years ago

Project changed from qe-yam to openQA Tests (public)
Status changed from Rejected to New

tinawang123 wrote:

But for this x86 case: https://openqa.suse.de/tests/10493761#step/disable_grub_timeout/40
The shortcut is alt-r

However, the test module is not using short cuts, but sending the right key until needle match: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/disable_grub_timeout.pm#L55-L57

And for some reason, SUT gets one or zero of the right keys and reacts, but then it stops responding.

See the original failure in https://openqa.suse.de/tests/10493761#step/disable_grub_timeout/40 or these ones in the SLES+HA job group:

https://openqa.suse.de/tests/10490612#step/disable_grub_timeout/45
https://openqa.suse.de/tests/10499541#step/disable_grub_timeout/46

As you can see this is failing at least in x86_64 and aarch64, and as reported sometimes SUT manages to react to 1 right key press (screen is left at Kernel Parameters tab), and sometimes to none (screen is left at Boot Code Options tab).

Jobs cloned into my instance also failed like the ones in osd:

http://mango.qa.suse.de/tests/5492#step/disable_grub_timeout/45

However sending an Alt+R before the send_key_until_needlematch does prevent the issue:

http://mango.qa.suse.de/tests/5491

I tried to confirm the issue manually by calling the installer from the ISO on a VM, but could not reproduce the issue over an SSH connection. However, restarting a job in openQA, taking control of it with Developer Mode, and then instructing it to stop at the installation/disable_grub_timeout module, and then connecting with vncviewer, I was able to reproduce the issue by sending the characters: Alt+C, Alt+B, tab, right, right

Not sure if the issue is related to VNC, or if the VM itself is stopping.

I am reopening this and changing the project to openQA Tests. Hope that is correct.

Actions

Copy link

Updated by xlai almost 2 years ago

FYI. A bug is opened, https://bugzilla.suse.com/show_bug.cgi?id=1208266.

Actions

Copy link

Updated by JERiveraMoya almost 2 years ago

Subject changed from Bootloader settings page - The shortcuts changed from alt-b to alt-t to Right key doesn't reach the SUT when switch tab to Bootloader Options

Actions

Copy link

#10

Updated by JERiveraMoya almost 2 years ago

Subject changed from Right key doesn't reach the SUT when switch tab to Bootloader Options to Right key doesn't reach the SUT when switching to tab Bootloader Options

Actions

Copy link

#11

Updated by JERiveraMoya almost 2 years ago

we can confirm that right key hang the VM in openQA and outside openQA with our own virtualization,
but using specific shortcut can workaround this situation.
Let's follow up in the bug then.

Actions

Copy link

#12

Updated by bschmidt almost 2 years ago

I've opened a PR with the workaround to get tests down the line done:

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16384

Actions

Copy link

#13

Updated by szarate almost 2 years ago

Related to action #124347: [sles][15-sp5][Build70.1][qe-core] Wrong product selected and failed to match needle added

Actions

Copy link

#14

Updated by szarate almost 2 years ago

@JERiveraMoya, how feasible do you see adding a similar case in the corresponding module using the libyui? to try and reproduce it there too by pressing right at the beginning of the screen, and then continuing with the normal test flow?

I'm thinking that if we manage to reproduce the issue there, we can safely deprecate the old installer workflows in all of our instances, as the libyui is way more reliable, and I doubt that people doing manual installation will be as reliable as openQA in following the same steps over and over :D

Actions

Copy link

#15