action #115133
open[desktop] windows_client_remotelogin: Windows desktop does not appear
Added by dimstar over 2 years ago. Updated 6 months ago.
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-remote-desktop-client4@64bit fails in
windows_client_remotelogin
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build 20220808
Expected result¶
Last good: 20220807 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dimstar over 2 years ago
NOTE:
remote-desktop-client4:investigate:retry: http://openqa.opensuse.org/t2505380 http://openqa.opensuse.org/t2505379
remote-desktop-client4:investigate:last_good_tests:95766380ce242e848b9f765bf4ec7131a6a2bb4d: http://openqa.opensuse.org/t2505382 http://openqa.opensuse.org/t2505381
Retry fails - retry with last_good_tests succeeded!
Investigation only lists:
- 9bced5a42 Fix sle systemd schedule
- 1e23513cb Support installing TW with ipxe menu in O3
- aad6df6a3 Schedule systemd upstream tests
- 0929d2148 Schedule systemd upstream tests dynamically
Updated by maritawerner over 2 years ago
- Subject changed from windows_client_remotelogin: Windows desktop does not appear to [desktop] windows_client_remotelogin: Windows desktop does not appear
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: remote-desktop-client4
https://openqa.opensuse.org/tests/2700308#step/windows_client_remotelogin/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.
Updated by openqa_review about 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: remote-desktop-client4
https://openqa.opensuse.org/tests/2883562#step/windows_client_remotelogin/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 112 days if nothing changes in this ticket.
Updated by openqa_review almost 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: remote-desktop-client4
https://openqa.opensuse.org/tests/3174985#step/windows_client_remotelogin/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 228 days if nothing changes in this ticket.
Updated by ph03nix almost 2 years ago
Updated link to test failure: https://openqa.opensuse.org/tests/3182739#step/windows_client_remotelogin/4
Updated by GraceWang over 1 year ago
From the two different results on the same build 20230326, we can see this failure might be caused by the performance of the openQA server or worker. The default timeout value is not enough in most cases.
https://openqa.opensuse.org/tests/3194638# (PASS)
https://openqa.opensuse.org/tests/3194466# (FAIL)
So increase the maximum waiting time for assert_screen "xrdp-login-screen"; can fix this issue.
Updated by GraceWang over 1 year ago
Short update:
- This issue can NOT be reproduced on local openQA env.
- Simply increase the maximum waiting time (from the default 30s to 300s) doesn't work.
- Need more time to dig the root cause of the failure.
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: remote-desktop-client4
https://openqa.opensuse.org/tests/3247811#step/windows_client_remotelogin/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 32 days if nothing changes in this ticket.
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: remote-desktop-client4
https://openqa.opensuse.org/tests/3364903#step/windows_client_remotelogin/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 84 days if nothing changes in this ticket.
Updated by slo-gin 6 months ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.