yahoo-eng-team team mailing list archive

[Claudio <claudio_enjoy@xxxxxxxxx>]

ok fixed !
set in compute machine : 
in nova.conf
 vncserverproxyclientaddress =  compute  ip 
 
in case of the grizzly guide is eth0 so 10.10.10.53


** Changed in: horizon
       Status: Incomplete => Fix Committed

** Changed in: nova
       Status: Invalid => Fix Committed

** Changed in: novnc (Ubuntu)
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1068602

Title:
  VNC Console in Dashboard fails to connect ot server (code: 1006)

Status in OpenStack Dashboard (Horizon):
  Fix Committed
Status in OpenStack Compute (Nova):
  Fix Committed
Status in “novnc” package in Ubuntu:
  Fix Committed

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_base_url=http://172.28.137.65:6080/vnc_auto.html
  vncserver_listen=0.0.0.0
  vncserver_proxyclient_address=172.28.137.65

  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-2064-4189-8d86-29df9b4ddaff | steveasles02 | ACTIVE | lab-test=10.0.10.10 |
  | ff8c5c9d-fb77-4451-b08c-4eee610f3b47 | steveaubu02  | ACTIVE | lab-test=10.0.10.11 |
  | db9952e3-ced8-4a70-8892-473b258731d6 | steveawin02  | ACTIVE lab-test=10.0.10.12 |
  | 17323ecc-1f93-4f4e-8139-e629a02a97e1 | steveawin04  | ACTIVE | lab-test=10.0.10.14 |
  +--------------------------------------+--------------+--------+-------------------------+
  root@iswubu33:/etc/nova# nova get-vnc-console ff8c5c9d-fb77-4451-b08c-4eee610f3b47 novnc
  +-------+------------------------------------------------------------------------------------+
  | Type  | Url                                                                                |
  +-------+------------------------------------------------------------------------------------+
  | novnc | http://172.28.137.65:6080/vnc_auto.html?token=0599f402-9150-462d-9c14-c2ed10c69492 |
  +-------+------------------------------------------------------------------------------------+

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1068602/+subscriptions