Actions
action #25186
closedExtend Debugging about status of a specific VNC Connection
Start date:
2017-09-11
Due date:
% Done:
0%
Estimated time:
Description
At the moment the feedback for a used VNC Connection during a job run is not sufficient
08:50:20.4222 10918 <<< testapi::select_console(testapi_console='x11', await_console=0)
/usr/lib/os-autoinst/consoles/vnc_base.pm:64:{
'port' => 5901,
'hostname' => '10.161.145.5',
'password' => 'nots3cr3t'
}
08:50:20.5923 10918 activate_console, console: x11, type:
08:50:20.5923 10918 activate_console called with generic type, no action
This information provided by the "select_console('x11')" call gives us no hints whether the connection was established or not.
The User can only refer to followup message like
considering VNC stalled, no update for 4.04 seconds
which is also kinda vague and the user can only guess that the connection is not there or died in between
Updated by coolo about 7 years ago
- Subject changed from [tools] Extend Debugging about status of a specific VNC Connection to Extend Debugging about status of a specific VNC Connection
- Status changed from New to Feedback
I have no idea what you expect to see. Please elaborate
Updated by okurz over 4 years ago
- Status changed from Feedback to Rejected
- Assignee set to okurz
no response. I also don't know how that could be done better.
Actions