Project

General

Profile

Actions

action #157282

open

[tools] openQA seems show wrong VNC access infromation in developer mode for NON-QEMU backend setups

Added by rfan1 8 months ago. Updated 6 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
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:

  1. ssh to vm directly
  2. vncviewer to access with ip addr of s390x-SUT with right port
  3. accss to s390x-SUT and use virsh console command to access the serial terminal/console

Please see attached file.

Suggestion

  1. OpenQA can show test the right VNC port or right method to access the setup
  2. For no qemu backend, openQA may show some warning messages that the VNC access information is not usable.

Files

Screenshot from 2024-03-15 09-35-53.png (83 KB) Screenshot from 2024-03-15 09-35-53.png wrong vnc access info rfan1, 2024-03-15 01:37

Related issues 1 (1 open0 closed)

Related to openQA Project - action #108515: [qe-tools] Incorrect vncviewer hostname shown in developer mode promptNew2022-03-17

Actions
Actions #1

Updated by okurz 8 months ago

  • Category set to Feature requests
  • Priority changed from Normal to Low
  • Target version set to Tools - Next
Actions #2

Updated by okurz 6 months ago

  • Target version changed from Tools - Next to future
Actions #3

Updated by szarate 3 months ago

  • Related to action #108515: [qe-tools] Incorrect vncviewer hostname shown in developer mode prompt added
Actions

Also available in: Atom PDF