action #48110
closed[functional][u][sporadic] test failed in different modules that switch from textmode terminal to graphical terminal - unable to login into the gnome session again but we should not even need to login when selecting the correct tty
0%
Description
Observation¶
openQA test in scenario opensuse-15.1-DVD-x86_64-extra_tests_on_gnome@64bit failed in
NM_wpa2_enterprise
This was fixed meanwhile in #45710 however.
Actually we just switch back from a text console to gdm, we detect that, enter the password in https://openqa.opensuse.org/tests/823304/file/video.ogv#t=126.72,126.74 and that is not accepted.
Acceptance criteria¶
Suggestions
- Find another test module or create one at least temporarily that switches to text console and back to "x11" and needing to login when just an unlock should do
- Newer versions of gdm are started twice, on tty2+tty7. If we switch to the "wrong one" we can login and are diverted to the other tty. We should ensure we select the tty where we are already logged in, i.e. we should not expect the user selection screen but the unlock screen of the already logged in user "bernhard"
Further details¶
Always latest result in this scenario: latest
Updated by okurz about 5 years ago
- Copied from action #45710: [functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays) added
Updated by okurz about 5 years ago
- Blocks action #47321: [functional][u][opensuse][sporadic] openSUSE Leap 15.1 fails updates_packagekit_gpk test added
Updated by okurz about 5 years ago
- Blocks action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock added
Updated by mgriessmeier almost 5 years ago
- Status changed from New to Rejected
- Assignee set to mgriessmeier
- Target version changed from Milestone 24 to Milestone 25
not happening for 4 months
Updated by okurz almost 5 years ago
- Status changed from Rejected to New
@mgriessmeier I think we misunderstood (again). Already in #45710 the real problem was not adressed, only symptoms. The problem is that the wrong tty is selected. Does not matter if the specified mentioned test looks stable now but the problem is still true. This ticket here is also a blocker to the two mentioned ones so we need to address the whole ticket chain properly. What ticket you use for which particular purpose I will leave to you of course. I came back to this ticket just because @lemon/coolgw asked in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6768 for feedback which is related.
Updated by okurz almost 5 years ago
- Related to action #53246: [desktop][tumbleweed] test fails in yast2_control_center added
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 25 to Milestone 26
Updated by mgriessmeier over 4 years ago
- Assignee deleted (
mgriessmeier) - Priority changed from Normal to High
- Target version changed from Milestone 26 to Milestone 27
for next grooming
Updated by SLindoMansilla over 4 years ago
- Status changed from New to Rejected
- Assignee set to mgriessmeier
Considering it resolved, as it was not failing since two months: https://openqa.opensuse.org/tests/1013759#next_previous
Updated by okurz over 4 years ago
- Status changed from Rejected to Workable
again and still #48110#note-5 . This is stated in the subject line as well as the acceptance criteria (someone only messed up the syntax but the text is there). Also the category is "Enhancement". Do we need to make this even more clear?
Updated by mgriessmeier over 4 years ago
- Assignee deleted (
mgriessmeier) - Target version changed from Milestone 27 to Milestone 28
then let's check this closer...
Updated by szarate over 4 years ago
- Status changed from Workable to New
I'm loving the ping pong on this ticket. Moving back to be groomed
Updated by SLindoMansilla over 4 years ago
- Priority changed from High to Low
Agreed to set it low prio as long as no new occurrence happens.
Updated by SLindoMansilla over 4 years ago
- Subject changed from [functional][u] test failed in NM_wpa2_enterprise unable to login into the gnome session again but we should not even need to login when selecting the correct tty to [functional][u][sporadic] test failed in NM_wpa2_enterprise unable to login into the gnome session again but we should not even need to login when selecting the correct tty
- Priority changed from Low to Normal
Just found new occurrence: https://openqa.opensuse.org/tests/1030766#step/ooffice/1
testapi::x11_start_program(program='oowriter')
testapi::send_key(key='alt-f2', do_wait=0)
Updated by SLindoMansilla over 4 years ago
- Has duplicate action #56852: test fails in ooffice added
Updated by SLindoMansilla over 4 years ago
- Priority changed from Normal to High
Updated by SLindoMansilla over 4 years ago
- Subject changed from [functional][u][sporadic] test failed in NM_wpa2_enterprise unable to login into the gnome session again but we should not even need to login when selecting the correct tty to [functional][u][sporadic] test failed in different modules that swtich from textmode terminal to graphical terminal - unable to login into the gnome session again but we should not even need to login when selecting the correct tty
- Status changed from New to Workable
- Priority changed from High to Low
- Estimated time set to 42.00 h
Updated by okurz over 4 years ago
- Related to action #36126: [functional][u] post_fail_hook matches on "text_login_root" before actual tty switch and therefore never logs in added
Updated by okurz over 4 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: create_hdd_gnome@svirt-xen-pv
https://openqa.suse.de/tests/3648677
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz over 4 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: create_hdd_gnome@svirt-xen-pv
https://openqa.suse.de/tests/3718200
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by mgriessmeier over 4 years ago
- Target version changed from Milestone 28 to Milestone 31
Updated by okurz over 4 years ago
- Related to action #57281: [sle][Migration][SLE15SP2] test fails in orphaned_packages_check - switch to tty failed added
Updated by okurz over 4 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: create_hdd_gnome@svirt-xen-pv
https://openqa.suse.de/tests/3766980
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz about 4 years ago
- Subject changed from [functional][u][sporadic] test failed in different modules that swtich from textmode terminal to graphical terminal - unable to login into the gnome session again but we should not even need to login when selecting the correct tty to [functional][u][sporadic] test failed in different modules that switch from textmode terminal to graphical terminal - unable to login into the gnome session again but we should not even need to login when selecting the correct tty
I doubt that the assessment from #48110#note-13 was entirely correct. Just because tests didn't immediately fail it doesn't mean that the issue wouldn't happen. I am pretty sure that https://openqa.opensuse.org/tests/1182632 linked to #63670 is an error of the same kind: tests/x11/toolkit/x11.pm calls select_console 'x11' coming from an X11 session but what we do is ask gnome to open another session on tty7 instead of re-using the existing one on tty2. This seems to take much longer than in before in the linked openQA job, probably because it's a common approach to reduce performance with new versions of gnome ;)
I suggest to prioritize this ticket higher again very soon to fix also #63670 and probably also other less well understood unclear issues of the same kind.
Updated by okurz about 4 years ago
- Related to action #63727: [opensuse][ppc64le] select_console "log-console" do not try to activate after a previous failure added
Updated by okurz about 4 years ago
- Related to action #63643: [opensuse] test fails in consoletest_finish and exiv2 due to failure in x11 console switch added
Updated by okurz about 4 years ago
- Related to action #63670: [functional][u] test fails in x11 - black screen added
Updated by hjluo about 4 years ago
- Related to action #63691: [SLE][Migration][SLE15SP2]test fails in patch_sle - switch to tty failed added
Updated by hjluo about 4 years ago
- Related to action #63694: [SLE][Migration][SLE15SP2]test fails in post_migration - switch to tty failed added
Updated by ggardet_arm about 4 years ago
Attempt to fix it: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9659
Updated by okurz about 4 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: online_sles15_pscc_basesys-srv_all_minimal_y
https://openqa.suse.de/tests/3984057
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 4 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: offline_sles15_media_lp-we-basesys-srv-desk-dev-contm-lgm-wsm_all_full
https://openqa.suse.de/tests/4177898
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by SLindoMansilla almost 4 years ago
- Status changed from Workable to Resolved
Verfied on O3: https://openqa.opensuse.org/tests/1258396#next_previous
Updated by SLindoMansilla almost 4 years ago
- Blocks deleted (action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock)
Updated by SLindoMansilla almost 4 years ago
- Has duplicate action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock added
Updated by okurz almost 4 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: offline_sles15_media_lp-we-basesys-srv-desk-dev-contm-lgm-wsm_all_full
https://openqa.suse.de/tests/4262798
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 4 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: offline_hpc12sp5_scc_def_full
https://openqa.suse.de/tests/4309721
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed