Project

General

Profile

action #63727

[opensuse][ppc64le] select_console "log-console" do not try to activate after a previous failure

Added by michel_mno almost 3 years ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-02-21
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

select_console "log-console" do not try to activate after a previous failure

  • initially investigating NM_wpa2_enterprise failure for ppc64le https://openqa.opensuse.org/tests/1180981#step/NM_wpa2_enterprise/35
  • found no captured data by post_fail_hook because select_console 'log-console' failed there.
  • that select_console 'log-console' only did an assert_screen with no action.

  • is it normal to not try to activate, while the previous select_console "log-console" + activate
    failed before and was followed by a "Loading a VM snapshot lastgood" ?

extract autoinst log
===
[2020-02-20T18:57:37.407 UTC] [debug] <<< testapi::wait_serial(timeout=1, quiet=undef, no_regex=0, regexp=qr/sysrq\s*:\s+show\s+blocked\s+state/i, expect_not_found=0, buffer_size=undef, record_output=undef)
[2020-02-20T18:57:38.519 UTC] [debug] >>> testapi::wait_serial: (?i:sysrq\s*:\s+show\s+blocked\s+state): ok
[2020-02-20T18:57:38.519 UTC] [debug] <<< testapi::send_key(key="ret", wait_screen_change=0, do_wait=0)
[2020-02-20T18:57:38.921 UTC] [debug] <<< testapi::select_console(testapi_console="log-console")
[2020-02-20T18:57:39.726 UTC] [debug] activate_console, console: log-console, type: console
[2020-02-20T18:57:39.727 UTC] [debug] <<< testapi::wait_still_screen(timeout=30, stilltime=1, similarity_level=47)
[2020-02-20T18:57:40.733 UTC] [debug] >>> testapi::wait_still_screen: detected same image for 1 seconds, last detected similarity is 1000000
[2020-02-20T18:57:40.733 UTC] [debug] <<< testapi::assert_screen(mustmatch=[
"tty5-selected",
"text-logged-in-root"
], timeout=60)
[2020-02-20T18:57:40.836 UTC] [debug] no match: 179.9s, best candidate: text-logged-in-root-20170321 (0.64)
...
[2020-02-20T19:00:41.705 UTC] [debug] >>> testapi::_check_backend_response: match=text-logged-in-root,tty5-selected timed out after 180 (assert_screen)
[2020-02-20T19:00:41.766 UTC] [debug] post_fail_hook failed: no candidate needle with tag(s) 'tty5-selected, text-logged-in-root' matched
[2020-02-20T19:00:41.772 UTC] [debug] Loading a VM snapshot lastgood
...
[2020-02-20T19:48:35.771 UTC] [debug] >>> testapi::_check_backend_response: match=network_manager-network_connected,network_manager-wrong_card_selected timed out after 90 (assert_screen)
[2020-02-20T19:48:35.866 UTC] [debug] no candidate needle with tag(s) 'network_manager-network_connected, network_manager-wrong_card_selected' matched
[2020-02-20T19:48:35.871 UTC] [debug] /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/x11/network/NM_wpa2_enterprise.pm:122 called testapi::select_console
[2020-02-20T19:48:35.871 UTC] [debug] <<< testapi::select_console(testapi_console="log-console")
[2020-02-20T19:48:36.677 UTC] [debug] /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/x11/network/NM_wpa2_enterprise.pm:122 called testapi::select_console
[2020-02-20T19:48:36.677 UTC] [debug] <<< testapi::assert_screen(mustmatch="log-console", no_wait=1, timeout=30)
[2020-02-20T19:48:36.777 UTC] [debug] no match: 89.9s, best candidate: root-console-bpfilter-msg-poo44156-20190122 (0.00)
...
[2020-02-20T19:50:07.730 UTC] [debug] no match: -0.5s, best candidate: root-console-rpc-msg-boo1116598-20191208 (0.04)
[2020-02-20T19:50:07.975 UTC] [debug] >>> testapi::_check_backend_response: match=log-console timed out after 90 (assert_screen)
[2020-02-20T19:50:08.034 UTC] [debug] post_fail_hook failed: no candidate needle with tag(s) 'log-console' matched
[2020-02-20T19:50:08.036 UTC] [debug] Loading a VM snapshot lastgood
===

Observation

openQA test in scenario opensuse-15.2-DVD-ppc64le-extra_tests_on_gnome@ppc64le fails in
NM_wpa2_enterprise

Test suite description

Maintainer: asmorodskyi, okurz. Extra tests which were designed to run on gnome

Reproducible

Fails since (at least) Build 72.1

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

autoinst.log (906 KB) autoinst.log michel_mno, 2020-02-21 15:44

Related issues

Related to openQA Tests - action #63643: [opensuse] test fails in consoletest_finish and exiv2 due to failure in x11 console switchResolved2020-02-20

Related to openQA Tests - action #48110: [functional][u][sporadic] test failed in different modules that switch from textmode terminal to graphical terminal - unable to login into the gnome session again but we should not even need to login when selecting the correct ttyResolved2019-01-04

History

#1 Updated by okurz almost 3 years ago

michel_mno wrote:

select_console "log-console" do not try to activate after a previous failure

  • initially investigating NM_wpa2_enterprise failure for ppc64le https://openqa.opensuse.org/tests/1180981#step/NM_wpa2_enterprise/35
  • found no captured data by post_fail_hook because select_console 'log-console' failed there.
  • that select_console 'log-console' only did an assert_screen with no action.

  • is it normal to not try to activate, while the previous select_console "log-console" + activate
    failed before and was followed by a "Loading a VM snapshot lastgood" ?
    […]

No, that's not normal. Something got confused as the consoles should be correctly handled after reverting to a snapshot, i.e. test should look for the login prompt and tty and not the logged in console. I am interested how this reproduces so I retriggered as https://openqa.opensuse.org/tests/1182614

#2 Updated by okurz almost 3 years ago

  • Related to action #63643: [opensuse] test fails in consoletest_finish and exiv2 due to failure in x11 console switch added

#3 Updated by okurz almost 3 years ago

  • Related to action #48110: [functional][u][sporadic] test failed in different modules that switch from textmode terminal to graphical terminal - unable to login into the gnome session again but we should not even need to login when selecting the correct tty added

#4 Updated by okurz almost 3 years ago

exiv2 failed in https://openqa.opensuse.org/tests/1182614#step/exiv2/2 . This to me looks like the same as #63670 : Probably a gnome performance regression triggered this but is obfuscated due to #48110

For the problem as reported here originally it is clearly reproduced in https://openqa.opensuse.org/tests/1182614#step/NM_wpa2_enterprise/35

I suggest to crosscheck with the x86_64 case and try to find a smaller reproducer, e.g. only run boot_to_desktop and the three wpa2 modules, e.g. clone with SCHEDULE=tests/boot/boot_to_desktop,tests/x11/network/hwsim_wpa2_enterprise_setup,tests/x11/network/yast2_network_use_nm,tests/x11/network/NM_wpa2_enterprise

#5 Updated by okurz almost 3 years ago

  • Subject changed from select_console "log-console" do not try to activate after a previous failure to [opensuse][ppc64le] select_console "log-console" do not try to activate after a previous failure

#6 Updated by okurz over 1 year ago

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period). This update was done as agreed within the SUSE QE Sync call 2021-09-01

#7 Updated by slo-gin 5 months ago

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