Actions
action #157282
open[tools] openQA seems show wrong VNC access infromation in developer mode for NON-QEMU backend setups
Start date:
2024-03-15
Due date:
% Done:
0%
Estimated time:
Description
Description¶
On non-qemu backend openQA setups, take s390x-kvm as an example, when I try to debug some issue with developer mode,
we can get the information from openqa web UI like:
You might be able to connect to the SUT at worker32.oqa.prg2.suse.org:5994 via VNC with shared mode enabled (eg. vncviewer workerxx.xx.org:5994 -Shared for TigerVNC)
.
However, it can not work for s390x-kvm setup since it is remote access. we may need to access the setup with below methods:
- ssh to vm directly
- vncviewer to access with ip addr of s390x-SUT with right port
- accss to s390x-SUT and use
virsh console
command to access the serial terminal/console
Please see attached file.
Suggestion¶
- OpenQA can show test the right VNC port or right method to access the setup
- For no qemu backend, openQA may show some warning messages that the VNC access information is not usable.
Files
Updated by szarate 3 months ago
- Related to action #108515: [qe-tools] Incorrect vncviewer hostname shown in developer mode prompt added
Actions