action #42524
closed[sle][migration][sle12sp4][backlog] test fails in yast2_migration - failed to select_console X11
Added by whdu over 5 years ago. Updated over 2 years ago.
0%
Description
It looks like script issue for select_console rather than a bug. Restart cases several times and it is same.
I do not have aarch64 machine to switch console for a test. Need further investigation.
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-Post-aarch64-om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64@aarch64 fails in
yast2_migration
Reproducible¶
Fails since (at least) Build 0378
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz over 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2175647
Updated by okurz over 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz over 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by ZejinXu over 5 years ago
Current observation:
Desktop was shown fine in first boot.
After registered system and upgraded 8 packages, the X11 console can't be selected.
Tried 'chvt 7' command and ctrl-alt-f7 from vncviewer. The vnc window would freeze after those commands, irresponsible to any keyboard input.Send command 'startx' would switch to/restart X11 successfully, but with 4 lines of error message.
Updated by okurz over 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz over 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz about 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz about 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz about 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz about 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz about 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz about 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz almost 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz almost 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz almost 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by okurz almost 5 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: om_proxyscc_sles12sp2_allpatterns_minimalupdate_by_yast_aarch64
https://openqa.suse.de/tests/2266486
Updated by leli about 4 years ago
- Subject changed from [sle][migration][sle12sp4] test fails in yast2_migration - failed to select_console X11 to [sle][migration][sle12sp4][backlog] test fails in yast2_migration - failed to select_console X11
Updated by okurz over 2 years ago
This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period). This update was done as agreed within the SUSE QE Sync call 2021-09-01
Updated by leli over 2 years ago
- Status changed from New to Rejected
- Estimated time set to 2.00 h
This is a very old ticket, I think it somehow like https://progress.opensuse.org/issues/97310, some package update cause gdm restart, anyway, currently we don't have the same issue on aarch64, I will close this issue for now, later if we found the same issue can re-open it.