Project

General

Profile

Actions

action #101608

closed

[Tumbleweed][security] test fails in add_users

Added by dimstar over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-10-28
Due date:
% Done:

100%

Estimated time:
4.00 h
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_users@64bit fails in
add_users

xterm ends up being started unfocused - as a result, all subsequent types go to the wrong application

Test suite description

Maintainer: llzhao@suse.de

Reproducible

Fails since (at least) Build 20211027

Expected result

Last good: 20211026 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by dimstar over 2 years ago

This was OK in snapshot 1026: https://openqa.opensuse.org/tests/1994633
In a rerun of the same 1026 snapshot, it failed: https://openqa.opensuse.org/tests/1998169

The investigation tap hints at nothing being changed that has impact:

182039c0d Support uefi guest installation registration
daac45daa SLE Micro: fix restart on s390x zVM
6da43d81b Implement Secure Boot support tests on aarch64

Actions #2

Updated by maritawerner over 2 years ago

  • Subject changed from test fails in add_users to [security] test fails in add_users
Actions #3

Updated by favogt over 2 years ago

Looks like a product bug to me. openQA doesn't appear do actively change focus, so for some reason the window manager decides not to focus the started xterm by itself.

Actions #4

Updated by llzhao over 2 years ago

  • Subject changed from [security] test fails in add_users to [Tumbleweed][security] test fails in add_users
  • Assignee set to llzhao
  • Estimated time set to 12.00 h
Actions #5

Updated by llzhao over 2 years ago

favogt wrote:

Looks like a product bug to me. openQA doesn't appear do actively change focus, so for some reason the window manager decides not to focus the started xterm by itself.

Thanks for the investigation:
It might also be possible that this code takes no effect (.../tests/security/yast2_users/add_users.pm):

     # Turn to x11 and start "xterm"
     select_console("x11");
     x11_start_program("xterm");
     become_root;
Actions #6

Updated by llzhao over 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
  • Estimated time changed from 12.00 h to 4.00 h

It is passed on recent builds: https://openqa.opensuse.org/tests/2019527

Actions #7

Updated by openqa_review over 2 years ago

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

This bug is still referenced in a failing openQA test: yast2_users
https://openqa.opensuse.org/tests/2053389

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions

Also available in: Atom PDF