[qe-sap][functional][sap] Screen is stuck in 'first_boot' on IPMI test
All IPMI jobs fail like this one: https://openqa.suse.de/tests/3767134#step/first_boot/8
Gnome screen is not shown after user connection:
[2020-01-08T22:54:34.356 CET] [debug] no change: 0.2s
[2020-01-08T22:54:34.456 CET] [debug] no change: 0.1s
[2020-01-08T22:54:34.556 CET] [debug] no change: 0.0s
[2020-01-08T22:54:43.082 CET] [debug] WARNING: check_asserted_screen took 8.42 seconds for 101 candidate needles - make your needles more specific
[2020-01-08T22:54:43.082 CET] [debug] no match: -0.1s, best candidate: displaymanager-sles4sap-nousers-20160513 (0.28)
[2020-01-08T22:54:43.353 CET] [debug] >>> testapi::_check_backend_response: match=authentication-required-user-settings,displaymanager,displaymanager-password-prompt,generic-desktop,screenlock,screenlock-password timed out after 90 (assert_screen)
[2020-01-08T22:54:43.486 CET] [debug] no candidate needle with tag(s) 'displaymanager, displaymanager-password-prompt, generic-desktop, screenlock, screenlock-password, authentication-required-user-settings' matched
[2020-01-08T22:54:43.486 CET] [debug] <<< testapi::check_screen(mustmatch="generic-login", timeout=0)
[2020-01-08T22:54:43.488 CET] [debug] NO matching needles for generic-login
Could be related to this bug: https://bugzilla.suse.com/show_bug.cgi?id=1158816
Further investigation is needed to check if it's a backend/test issue or a product bug.
- Priority changed from High to Normal
This ticket was set to "High" priority but was not updated within 120 days which is 4 times the period of the SLO for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Normal".