Project

General

Profile

Actions

action #88768

closed

[sle][migration][sle15sp3][regression] test fails in install_service - failed to unlock screen on s390x

Added by leli about 3 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-02-19
Due date:
% Done:

10%

Estimated time:
8.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP3-Regression-on-Migration-from-SLE15-SPx-s390x-online_sles15sp2_pscc_basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm_all_full@s390x-kvm-sle12 fails in
install_service

The different behavior for unlock system on different system version, such as on SLES15SP3 it will directly show the login window for bernhard, while on SLES15SP2 is this issue. If this is not a bug, we need deal with the different behavior on different system versions, to choose user to unlock the system.

Test suite description

Reproducible

Fails since (at least) Build 23.1

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by leli about 3 years ago

  • Subject changed from [sle][migration][sle15sp3][regression] test fails in install_service to [sle][migration][sle15sp3][regression] test fails in install_service - need choose Bernhard to unlock screen
Actions #2

Updated by leli about 3 years ago

  • Subject changed from [sle][migration][sle15sp3][regression] test fails in install_service - need choose Bernhard to unlock screen to [sle][migration][sle15sp3][regression] test fails in install_service - failed to unlock screen on s390x
Actions #3

Updated by leli about 3 years ago

It seems this issue won't happened on SLE12, https://openqa.nue.suse.com/tests/5506788#step/install_service/28

Actions #4

Updated by leli about 3 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

Add workaround of mouse move to quit the screen lock:

Wait https://openqa.nue.suse.com/tests/5564495 and https://openqa.nue.suse.com/tests/5564496 to verify.

Actions #5

Updated by coolgw about 3 years ago

  • Estimated time set to 16.00 h
Actions #6

Updated by leli about 3 years ago

It may for the gdm restarted after vnc reconnected, I will try to add a loop to use mouse_set to make system recall.

Wait http://openqa.nue.suse.com/tests/5565431.

Actions #7

Updated by leli about 3 years ago

  • Status changed from In Progress to Rejected

filed a bug for this issue https://bugzilla.suse.com/show_bug.cgi?id=1182958, so just reject the ticket and we can re-open it if needed.

Actions #8

Updated by leli about 3 years ago

  • Status changed from Rejected to In Progress

Currently I think it is for the vnc configure issue which cause the vnc connection lost and re-connect after press the lock screen button on s390x.

I tried to add console/yast2_vnc to configure vnc correctly before the users test.
Wait https://openqa.nue.suse.com/tests/5590234 to verify.

Actions #9

Updated by leli about 3 years ago

Can't reproduce this issue manually on the same image.

Actions #10

Updated by leli about 3 years ago

Try to update the qcow with correct vnc configuration.

https://openqa.nue.suse.com/tests/5620618

Actions #11

Updated by leli about 3 years ago

fix the send key issue in yast2-vnic, re-run and wait https://openqa.nue.suse.com/tests/5625794#details

Actions #12

Updated by leli about 3 years ago

Reject this ticket again and track it in bsc#1182958 which re-assigned to vnc dev team now.

Actions #13

Updated by leli about 3 years ago

  • Status changed from In Progress to Rejected
Actions #14

Updated by coolgw almost 3 years ago

  • Estimated time changed from 16.00 h to 8.00 h
Actions

Also available in: Atom PDF