Bug 1619218 - remote-viewer always shows "Waiting for display 1" when using virtctl to connect vm
Summary: remote-viewer always shows "Waiting for display 1" when using virtctl to conn...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 1.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 1.3
Assignee: Marc Sluiter
QA Contact: Gabriel Szasz
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-20 11:21 UTC by zhe peng
Modified: 2019-01-08 14:27 UTC (History)
7 users (show)

Fixed In Version: kubevirt-0.9.4-2.gd763ed8.6e00282 cnv-libvirt-container-v1.3.0-3 virt-api-container-v1.3.0-11 virt-controller-container-v1.3.0-13 virt-handler-container-v1.3.0-12 virt-launcher-container-v1.3.0-13
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-08 14:27:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 3 Nelly Credi 2018-08-21 12:13:05 UTC
not targeted for the 1st z-stream

Comment 4 Marc Sluiter 2018-08-21 20:57:02 UTC
Hi, I can't reproduce this upstream with Openshift 3.10, kubevirt v0.6.4-cnv-1.1 (was tagged today) and a Fedora VM. Can you please provide some more info on your environment? Does virtctl console work? And please post your VM(I) spec. Thanks.

Comment 5 zhe peng 2018-08-22 02:20:18 UTC
virtctl console worked for me, i use spec under kubevirt/cluster/examples/
i have try different spec, but all have this issue.

Comment 6 Marc Sluiter 2018-08-22 07:35:21 UTC
On which cluster are you testing? Kubernetes/Openshift? Which version (kubectl version / oc version)? Is it running locally on your machine or remote?
And what kubevirt version are you using (virtctl version)?

Comment 9 Nelly Credi 2018-09-04 12:31:17 UTC
@Marc any updates?

Comment 10 Marc Sluiter 2018-09-04 12:47:55 UTC
@Nelly please see my comment above, I need more info about the environment in order to reproduce the problem

Comment 11 zhe peng 2018-09-05 03:21:28 UTC
Hi Marc
I already put the info in comment 7 & comment 8, need anything else?

Comment 12 Marc Sluiter 2018-09-05 07:12:11 UTC
Hi Zhe, in a discussion with Nelly yesterday it turned out that I can't see private comments, that's why I didn't react and asked for info again, sorry! Got your info from Nelly now, and I requested the missing permission. Will try to reproduce the issue today, and update here as soon as I found out what the problem is.

Comment 13 Marc Sluiter 2018-09-09 18:48:12 UTC
I still can't reproduce this on my machine with the same KubeVirt version. Can you please link me to an environment where I can reproduce this, with short steps on what I need to do (I'm not familiar with the OpenStack UI yet)? The one from the description (which I also could't see earlier without the private comment permission) doesn't work anymore. Thx.

Comment 15 Marc Sluiter 2018-09-11 18:42:56 UTC
After a lot of debugging I finally found the difference to my local setup: I didn't use the Openshift *CRI-O* version.
I can now reproduce the issue. Thanks for providing the test environment! Unfortunately I still have no clue why this fails in the end, will dig deeper into it.

Comment 16 Nelly Credi 2018-09-13 14:30:28 UTC
In general its a blocker, but since it doesnt affect customer0, we are ok with releasing 1.2 without this functionality

Comment 17 Marc Sluiter 2018-09-17 21:20:10 UTC
I finally found the cause AND a fix for this, see https://github.com/kubevirt/kubevirt/pull/1516

Comment 18 Yan Du 2018-10-16 03:48:59 UTC
Test on OCP3.11 + kubevirt v0.9.1, virtctl vnc works well with both fedora and windows vms. will verify the issue after getting cnv 1.3 build.

Comment 19 Yan Du 2018-11-07 09:35:43 UTC
Test on OCP 3.11 + CNV 1.3, virtctl vnc works well.
openshift v3.11.16
kubernetes v1.11.0+d4cacc0

Comment 20 Nelly Credi 2018-11-07 14:43:03 UTC
@Marc, could you please add 'fixed in' version?

Comment 21 Pan Ousley 2018-11-07 16:35:40 UTC
There is a Known Issue for this in the current 1.3 Release Notes (holdover from 1.2). IIUC the bug is fixed in 1.3, so I should remove that from the 1.3 docs. Nelly can you confirm?

Comment 22 Marc Sluiter 2018-11-08 08:47:36 UTC
@Nelly, that was fixed a while ago, hard to find the earliest downstream build which contained the fix. So I just added the latest, I hope that's ok :)

Comment 23 Pan Ousley 2018-11-15 21:41:27 UTC
Removing the Known Issue from the 1.3 docs. Let me know if it should be added back in.


Note You need to log in before you can comment on or make changes to this bug.