action #44978

[ipmi unstability] jobs got blue screen making openqa needle match does not work

Added by xlai about 1 year ago. Updated 5 months ago.

Status:RejectedStart date:11/12/2018
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Feature requests
Target version:-
Difficulty:
Duration:

Description

The blue screen looks like https://openqa.suse.de/tests/2319257#step/boot_from_pxe/25, and when it happens, needle matching mechenism of openqa will not work(creating new needle based on the blue screen not work and with such needle when retrigger jobs, job will fail at any needle matching).


Related issues

Related to openQA Tests - action #36027: [sle][functional][u][ipmi] test fails in boot_from_pxe - ... Workable 20/10/2017

History

#1 Updated by xlai about 1 year ago

  • Related to action #36027: [sle][functional][u][ipmi] test fails in boot_from_pxe - pxe boot menu doesn't show up at all added

#2 Updated by xlai about 1 year ago

It is a traditional ipmi unstability phonomenon. Let's see whether the general solution of issue #36027 can fix it.

#3 Updated by xlai about 1 year ago

  • Subject changed from [ipmi] jobs got blue screen making openqa needle match does not work to [ipmi unstability] jobs got blue screen making openqa needle match does not work

#4 Updated by SLindoMansilla about 1 year ago

  • Category set to Bugs in existing tests

#5 Updated by okurz about 1 year ago

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

This bug is still referenced in a failing openQA test: prj2_host_upgrade_sles15_to_developing_xen
https://openqa.suse.de/tests/2360835

#6 Updated by okurz about 1 year ago

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

This bug is still referenced in a failing openQA test: prj2_host_upgrade_sles15_to_developing_kvm
https://openqa.suse.de/tests/2441475

#7 Updated by okurz about 1 year ago

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

This bug is still referenced in a failing openQA test: gi-guest_sles11sp4-on-host-developing-kvm
https://openqa.suse.de/tests/2485705

#8 Updated by okurz 12 months ago

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

This bug is still referenced in a failing openQA test: gi-guest_developing-on-host_sles12sp4-xen
https://openqa.suse.de/tests/2529547

#9 Updated by okurz 11 months ago

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

This bug is still referenced in a failing openQA test: prj4_guest_upgrade_sles12sp4_on_sles12sp4-kvm
https://openqa.suse.de/tests/2785240

#10 Updated by xlai 11 months ago

  • Project changed from openQA Tests to openQA Project
  • Category changed from Bugs in existing tests to 128
  • Priority changed from Normal to High

#11 Updated by coolo 10 months ago

What needle fails where? A little bit more context, please

#12 Updated by xlai 10 months ago

@coolo, thanks for noticing this ticket.

Yes, the process is:
When blue screen issue happens on ipmi machines, tried to add a needle based on https://openqa.suse.de/tests/2319257#step/boot_from_pxe/25 with sshd-server-started tag, which aims to make assert_screen 'sshd-server-started' pass when this specific blue screen issue happens again.
However after this blue needle added, from the next triggered job, all needle matching will not work any more. That is to say from the first needle matching, https://openqa.suse.de/tests/2319257#step/boot_from_pxe/1, it will never succeed in needle match, although the screen should be exactly correct and matched.
But if remove that blue screen needle https://openqa.suse.de/tests/2319257#step/boot_from_pxe/25 from needle directory, needle match works again.

#13 Updated by coolo 10 months ago

Well, black font on dark blue looks to openQA eyes (and to most human eyes) as pure black, so there is no way you can differ this.

So you better research if there is some key combination that resets the terminal (ctrl-L comes to mind) that you can press in case you didn't see the ssh needle in time. It's a design decision for openQA to look like a half blind snake and while technically we could offer HD needles, it won't happen soon.

#14 Updated by xlai 10 months ago

@coolo, thanks for the suggestion. Sorry, would you please explain further, in your suggestion, what are expected to happen when such key to reset the terminal are sent? Screen refreshed and redisplayed without the blue screen background?

Actually for this specific case, when the 'sshd-server-started' screen shows, it means ssh service started, and next step of test is to start the root-ssh console to type yast.ssh to trigger installation. So what we want to find is a way to workaround this blue screen issue and check whether sshd starts to start later ssh session.

#15 Updated by okurz 8 months ago

  • Category changed from 128 to Feature requests

#16 Updated by coolo 5 months ago

  • Status changed from New to Rejected

I don't see anything we can do about it.

Also available in: Atom PDF