action #88193
[qe-core] virtio-terminal is missing for non root users
0%
Description
Calling $self->select_user_serial_terminal;
(alias for $self->select_serial_terminal(0);
) in test on a QEMU backend results in the following error:
[2021-01-25T14:06:53.271 CET] [debug] tests/x11/ghostscript.pm:45 called opensusebasetest::select_serial_terminal -> lib/opensusebasetest.pm:1243 called testapi::select_console [2021-01-25T14:06:53.271 CET] [debug] <<< testapi::select_console(testapi_console="virtio-terminal") console virtio-terminal does not exist at /usr/lib/os-autoinst/backend/driver.pm line 86. [2021-01-25T14:06:53.319 CET] [info] ::: basetest::runtest: # Test died: Can't call method "select" on an undefined value at /usr/lib/os-autoinst/backend/baseclass.pm line 667.
The select_serial_terminal
method expects to have a non-root virtio console named virtio-terminal
but lib/susedistribution.pm
does not define any non-root virtio consoles.
History
#2
Updated by okurz 2 months ago
- Subject changed from [tools][qe-core] virtio-terminal is missing for non root users to [qe-core] virtio-terminal is missing for non root users
- Priority changed from Normal to Low
- Target version set to future
This should be fixable by non-tools-team contributions. Considering the backlog limit for SUSE QE Tools setting to "future" for now.
#4
Updated by okurz 2 months ago
- Target version set to future
szarate can you please help a bit with explaining what you want to achieve with changing the prio again and deleting the target version? I set the target version as we use it for the "SUSE QE Tools" team backlog and all issues within the openQA issue tracker have a target version so that they are "triaged", otherwise these tickets reappear on the "to be triaged" ticket query so in our current process we need either that or we move the issue to another issue tracker. As you have kept the marker "qe-core" in the subject I assume you are still fine with having that on the backlog of said team so maybe the other change was by mistake when you updated the ticket or something, hence setting the target version "future" again.