action #80776
closedopenQA Project - coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues
openQA Project - coordination #62420: [epic] Distinguish all types of incompletes
[jeos] job incomplete auto_review:"(?s)(podman|docker).*Virtio terminal and svirt serial terminal do not support send_key":retry
0%
Description
Observation¶
sle-15-SP3-JeOS-for-kvm-and-xen-x86_64-jeos-container-engines_and_tools@uefi-virtio-vga (latest job for this scenario)
in https://openqa.suse.de/tests/5138355/file/autoinst-log.txt
[2020-12-06T21:41:33.097 CET] [debug] <<< testapi::send_key(key="ctrl-d", do_wait=0, wait_screen_change=0)
[37m[2020-12-06T21:41:33.098 CET] [debug] Backend process died, backend errors are reported below in the following lines:
Virtio terminal and svirt serial terminal do not support send_key. Use
type_string (possibly with an ANSI/XTERM escape sequence), or switch to a
console which sends key presses, not terminal codes.
at /usr/lib/os-autoinst/backend/baseclass.pm line 787.
same now encountered in https://openqa.opensuse.org/tests/1509452
Steps to reproduce¶
Find jobs referencing this ticket with the help of
https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label ,
call openqa-query-for-job-label poo#80776
Problem¶
The message already states it :)
Further details¶
Link to sle-15-SP3-JeOS-for-kvm-and-xen-x86_64-jeos-container-engines_and_tools@uefi-virtio-vga latest
and opensuse-15.3-JeOS-for-kvm-and-xen-x86_64-jeos-containers@64bit_virtio-2G latest
Workaround¶
Retrigger
Updated by okurz almost 4 years ago
- Copied from action #78055: job incomplete exiting prematurely before reaching needle check timeout auto_review:"(?s)called testapi::assert_screen.*no match: [^-0]+\.[0-9]s,[^\n]*\n[^\n]*backend process exited: 0.*\[autotest\] process exited: 1":retry added
Updated by okurz almost 4 years ago
- Copied to action #80778: job incompletes with "Virtio terminal and svirt serial terminal do not support send_key", we should change the reason message to be ignored by auto-review, but be clear for the test maintainer added
Updated by okurz almost 4 years ago
- Subject changed from [jeos] job incomplete auto_review:"(?s)openqa.suse.de.*Virtio terminal and svirt serial terminal do not support send_key":retry to [jeos] job incomplete auto_review:"(?s)openqa.(suse.de|opensuse.org).*Virtio terminal and svirt serial terminal do not support send_key":retry
Updated by okurz almost 4 years ago
- Subject changed from [jeos] job incomplete auto_review:"(?s)openqa.(suse.de|opensuse.org).*Virtio terminal and svirt serial terminal do not support send_key":retry to [jeos] job incomplete auto_review:"(?s)(podman|docker).*Virtio terminal and svirt serial terminal do not support send_key":retry
Updated by MDoucha almost 4 years ago
This looks like inconsistent console state in os-autoinst after snapshot reload. The worker thinks it switched to VNC console but it still uses cached serial_screen to actually read and write. serial_screen doesn't support send_key() and throws that particular exception. But script_output() is using a code path which cannot be executed when the current console is a serial terminal.
https://github.com/os-autoinst/os-autoinst/blob/a505c79063d0680ff6d761590ad7700f69d79ff3/distribution.pm#L254
Updated by jlausuch over 3 years ago
- Project changed from openQA Tests to 208
- Category deleted (
Bugs in existing tests)
Updated by ybonatakis over 3 years ago
- Assignee set to ybonatakis
not reproduced for 4 months since build 6.1. close it