Bug 1216200 - [Build 538.1] openQA test fails in system_prepare - fails to switch to tty6 after upgraded to 15.6
Summary: [Build 538.1] openQA test fails in system_prepare - fails to switch to tty6 a...
Status: RESOLVED DUPLICATE of bug 1211219
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Leap 15.6
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL: https://openqa.opensuse.org/tests/364...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-13 07:25 UTC by Max Lin
Modified: 2023-10-26 11:27 UTC (History)
0 users

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Max Lin 2023-10-13 07:25:21 UTC 
## Observation

after upgrade the system to 15.6, switch to tty6 fails to work, it can be displaymanager or the default launched tty doesn't match, need a deeper look. The tricky thing is this issue happened on from the system before Leap 15.1, ie. migrating from 15.2 or the version above doesn't have this issue.

openQA test in scenario opensuse-15.6-DVD-x86_64-upgrade_Leap_42.3_gnome@64bit fails in
[system_prepare](https://openqa.opensuse.org/tests/3640963/modules/system_prepare/steps/2)

## Test suite description



## Reproducible

Fails since (at least) Build [517.2](https://openqa.opensuse.org/tests/3533054)


## Expected result

Last good: [511.1](https://openqa.opensuse.org/tests/3513979) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=upgrade_Leap_42.3_gnome&version=15.6)
Comment 1 Max Lin 2023-10-26 11:27:11 UTC 
it's the same error, the same problem we had in 15.5 as described in bsc#1211219

*** This bug has been marked as a duplicate of bug 1211219 ***