action #103863
closed[JeOS 15-SP3 QU2 hyperv] - test fails in firstrun - setterm -blank 0' timed out
0%
Description
Observation¶
openQA test in scenario sle-15-SP3-JeOS-for-MS-HyperV-QR-x86_64-jeos-extratest@svirt-hyperv fails in
firstrun
It also fails in svirt-hyperv-uefi : https://openqa.suse.de/tests/7828827#step/firstrun/18
At first, I thought it was just a timeout issue in testapi and I tried to increase it:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13852
but the VRs were failing at the same point, so it's not just a timeout.
There is some issue right after calling assert_script_run
[2021-12-10T13:40:11.752264+01:00] [debug] tests/jeos/firstrun.pm:145 called testapi::assert_script_run
[2021-12-10T13:40:11.752502+01:00] [debug] <<< testapi::type_string(string="; echo tnTFj-\$?- > /dev/ttyS0\n", max_interval=250, wait_screen_changes=0, wait_still_screen=0, timeout=30, similarity_level=47)
[2021-12-10T13:40:12.868906+01:00] [debug] tests/jeos/firstrun.pm:145 called testapi::assert_script_run
[2021-12-10T13:40:12.869178+01:00] [debug] <<< testapi::wait_serial(timeout=90, buffer_size=undef, expect_not_found=0, quiet=undef, record_output=undef, no_regex=0, regexp=qr/tnTFj-\d+-/u)
2021/12/10 13:41:04 socat[24720] E connect(5, AF=2 10.100.101.33:10012, 16): Connection timed out
But I don't know why this happens, but some other hyper-v tests are passing, e.g. https://openqa.suse.de/tests/7820913
Test suite description¶
Reproducible¶
Fails since (at least) Build 3.3.7
Expected result¶
Last good: 3.3.7 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by szarate about 3 years ago
- Related to action #97745: [virtualization][hyperv] ensure_serialdev_permissions fails for hyperv added
Updated by szarate about 3 years ago
Pavel's comment seems to be a very good hint: https://progress.opensuse.org/issues/97745#note-18
Updated by jlausuch almost 3 years ago
- Status changed from Workable to Feedback
I don't see this issue in latest builds.
https://openqa.suse.de/tests/7999362#next_previous
Updated by apappas almost 3 years ago
IMHO the issue may not be present on the latest builds, because to trigger it you need to stress the hypervisor, so that the serial consoles get wonky.
Updated by jlausuch almost 3 years ago
- Due date set to 2022-03-01
Yeah, looks like it really depends on the infra... I will just keep it in Feedback for a while and close (1st March) if it's not referenced again.
Updated by mloviska almost 3 years ago
- Status changed from Feedback to Rejected
I haven't seen it for a while, therefore closing. Feel free to reopen if you see it again. Thanks!