yahoo-eng-team team mailing list archive

[KamalaVenkatesh <1741841@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description:
When try to open an instance VNC console, we get an error message (such as "failed to connect server; code=1006) after some time.For the initial 5 min it work successfully.(pike release)

Workaround: 
browser refresh it eventually works.

Logs:
nova-consoleauth.log
INFO nova.consoleauth.manager [req-0db1a667-bba0-427d-ba0b-4f03ecf1bcca - - - - -] Checking Token: f2c6eac1-ad7a-4bbf-8952-7e7fd5c4ae75, False

nova-novncproxy.log
INFO nova.console.websocketproxy [req-0db1a667-bba0-427d-ba0b-4f03ecf1bcca - - - - -] handler exception: The token 'f2c6eac1-ad7a-4bbf-8952-7e7fd5c4ae75' is invalid or has expired

Environment
-3 compute nodes and 2 controller nodes 
-nova.conf on compute node has,
 vnc_enabled = True
 novnc_enabled = True
 vnc_keymap = en-us
 vncserver_listen = 0.0.0.0
 vncserver_proxyclient_address = 10.20.0.137
 novncproxy_base_url = http://10.20.3.101:6080/vnc_auto.html

-nova.conf on controller node has [cache] section
 [cache]
 enabled = true
 backend = oslo_cache.memcache_pool
 memcache_servers = 10.20.0.142:11211,10.20.0.164:11211,10.20.0.152:11211

Steps to reproduce 
login to the dashboard as a project user, spawn a VM, from the drop down - select VNC console. Able to connect to vnc console for initial 5-7 min after this not able to connect.An empty VNC window appears but cannot connect to the VM with an error "Failed to connect to server(code:1006)".
100% repeatable

any guidance on resolve this would be really appreciated

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1741841

Title:
  VNC console fails to connect

Status in OpenStack Compute (nova):
  New

Bug description:
  Description:
  When try to open an instance VNC console, we get an error message (such as "failed to connect server; code=1006) after some time.For the initial 5 min it work successfully.(pike release)

  Workaround: 
  browser refresh it eventually works.

  Logs:
  nova-consoleauth.log
  INFO nova.consoleauth.manager [req-0db1a667-bba0-427d-ba0b-4f03ecf1bcca - - - - -] Checking Token: f2c6eac1-ad7a-4bbf-8952-7e7fd5c4ae75, False

  nova-novncproxy.log
  INFO nova.console.websocketproxy [req-0db1a667-bba0-427d-ba0b-4f03ecf1bcca - - - - -] handler exception: The token 'f2c6eac1-ad7a-4bbf-8952-7e7fd5c4ae75' is invalid or has expired

  Environment
  -3 compute nodes and 2 controller nodes 
  -nova.conf on compute node has,
   vnc_enabled = True
   novnc_enabled = True
   vnc_keymap = en-us
   vncserver_listen = 0.0.0.0
   vncserver_proxyclient_address = 10.20.0.137
   novncproxy_base_url = http://10.20.3.101:6080/vnc_auto.html

  -nova.conf on controller node has [cache] section
   [cache]
   enabled = true
   backend = oslo_cache.memcache_pool
   memcache_servers = 10.20.0.142:11211,10.20.0.164:11211,10.20.0.152:11211

  Steps to reproduce 
  login to the dashboard as a project user, spawn a VM, from the drop down - select VNC console. Able to connect to vnc console for initial 5-7 min after this not able to connect.An empty VNC window appears but cannot connect to the VM with an error "Failed to connect to server(code:1006)".
  100% repeatable

  any guidance on resolve this would be really appreciated

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