Kubevirt: virtctl vnc is unhelpful

[pkliczewski]

When i run:

virtctl vnc <vmname>

I get:

E0412 14:01:50.703176 567 vnc.go:103] exit status 1

I would like to understand why it is not working.

[pkliczewski]

I downloaded virtctl from here.

[karmab]

this seems to be the error reported from remote-viewer

[davidvossel]

I can make it more obvious that the string is coming from remote-viewer

[davidvossel]

917 I made the log message more descriptive in order to indicate that the error is coming from remote-viewer.

@pkliczewski Are you still unable to connect to vnc? Do you have any idea why remote-viewer was failing?

[rmohr]

917 I made the log message more descriptive in order to indicate that the error is coming from remote-viewer.

I think that we should also not swallow stdout/stderr of remote-viewer. Especially if something goes wrong.

[pkliczewski]

@davidvossel I downloaded virtctl from here and run it like this:

[root@master ~]# ./virtctl vnc win-2016
E0418 11:26:53.397374 11139 vnc.go:103] exit status 1

[fromanirh]

While trying to troubleshoot virtctl vnc I run in the same issues, so I added some fix to make it easier to understand what's wrong, and posted them in https://github.com/kubevirt/kubevirt/pull/934

[fabiand]

@fromanirh do you think this issue is resolved?

We actually had a person on slack which was affected by insufficient error messages :)

[fromanirh]

@fabiand I think so. My PR https://github.com/kubevirt/kubevirt/pull/934 was approved, I think we can set this issue resolved once the PR gets merged.

[rmohr]

@fromanirh merged. Can you open a PR on the user-guide and add a few comments to the virtcl vnc documentation about debugging?

[fromanirh]

@rmohr ack - and thanks for the merge

[fromanirh]

@rmohr @fabiand done: https://github.com/kubevirt/user-guide/pull/81