Project

General

Profile

action #41795

[qam] test fails in reboot_gnome - needle warns about other logged in users

Added by bfilho over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
coolo
Category:
Bugs in existing tests
Target version:
-
Start date:
2018-09-28
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-Server-DVD-Updates-x86_64-qam-allpatterns@64bit fails in
reboot_gnome

Reproducible

Fails since (at least) Build 20180928-2

Expected result

Last good: 20180928-1 (or more recent)

Further details

Always latest result in this scenario: latest

It seems that some messages changed in the dialog boxes, would require some re-needle.

History

#1 Updated by okurz over 4 years ago

  • Subject changed from test fails in reboot_gnome to [qam] test fails in reboot_gnome - needle warns about other logged in users
  • Priority changed from Normal to High

please try to find more expressive subject lines and not just accept what the ticket reporting template suggests. Also, for [qam] specific issues also add [qam] in the subject line.

To me it seems as if other users would be logged in and therefore the reboot authentication dialog shows a different message. Though I do not see in which test module another user would be logged in. Assuming that this did not happen I consider this a product bug introduced recently, see https://openqa.suse.de/tests/2106568#next_previous

#2 Updated by coolo over 4 years ago

  • Status changed from New to Resolved

The comparision between last good (https://openqa.suse.de/tests/2103431) and first fail (https://openqa.suse.de/tests/2106108) shows that prepare_system_update was introduced by
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5826

Looking at the verification runs: the needles used there don't actually check the message - so it doesn't matter there that the newly introduced test leaves a user logged in. So just reneedling looks the way to go.

So I created shutdown-auth-other-users-20181001

#3 Updated by okurz over 4 years ago

  • Assignee set to coolo

ok, good. I missed the different test schedule then.

#4 Updated by coolo over 4 years ago

That would be a little obsessive - the number of verification runs in that PR is already huge

Also available in: Atom PDF