VNC Console in Dashboard fails to connect ot server (code: 1006)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Dashboard (Horizon) |
Invalid
|
Undecided
|
Gabriel Hurley | ||
novnc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This is a multi server installation of openstack with 1 'Cloud controller ' runnign all nova services + 2 compute nodes
I have installed both nova-novncproxy and novnc packages and it appears novnc itself is working ok.
All hosts are 12.04 using the Ubuntu cloud repo for folsom, all updated in the last week.
my nova.conf is as follows:
novncproxy_
vncserver_
vncserver_
my host IP is 172.28.137.65 for Cloud controller
summary -
I can request a noVNC url as follows:
| ID | Name | Status | Networks |
+------
| 0c6ce9b3-
| ff8c5c9d-
| db9952e3-
| 17323ecc-
+------
root@iswubu33:
+------
| Type | Url |
+------
| novnc | http://
+------
i can connect to each VM succesfully from Chrome or firefox via VNC from this URL.
I DO have to refresh the window 2-3 times for the connection to be established, this may be an issue in itself ???.
So far so good, i now want to access this via the Folsom dashboard so i login to the dashboard as a project user, select a VM instance of which I as a user have launched , from the drop down - select VNC console.
VNC Console then appears but is unable to connect to the same Vms that i could access before directly from the nova get-vnc-console command.
so in summary, i cant access the VNC console in the dashboard
error reported back in the browser is a 'failed to connect to server (code: 1006)
I CAN connect via nova get-vnc-console <serverid> novnc
Steps to reproduce -
login to the dashboard as a project user, select a VM instances of which I as a user have launched , from the drop down - select VNC console. An empty VNC window appears but cannot connect to the VM
100% repeatable
current Firefox browser (V16.0.1), shockwave flash version 11.4.402.287
current Chrome (Version 22.0.1229.94 m)
any guidance on how to workaround or resolve would be really appreciated
Changed in novnc (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
status: | Fix Released → Invalid |
Changed in nova: | |
status: | Fix Released → Invalid |
The fact that you're having to try to connect multiple times is suspicious. If your setup were completely working correctly it would connect every time.
The Nova team is much better equipped to debug NoVNC issues than the Horizon team. All Horizon does is get that URL and connect to it in an iFrame.
That said, one reason I *have* seen the NoVNC service fail intermittently like that is in multi-node/proxied systems where you're running multiple NoVNC services (such as on each node) and so when the dashboard tries to connect to the URL that the API returned it ends up hitting a service that didn't originate the URL/token so it gets rejected. That may or may not be the case here, but is one avenue worth investigating.
All in all I'm pretty sure this isn't a Horizon bug, at least without further details.