VNC console fails to connect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Low
|
Unassigned |
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-consoleaut
INFO nova.consoleaut
nova-novncproxy.log
INFO nova.console.
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_
novncproxy_
-nova.conf on controller node has [cache] section
[cache]
enabled = true
backend = oslo_cache.
memcache_servers = 10.20.0.
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
There is the 'token_ttl' parameter in nova configuration file (nova.conf).
It defines expiration time of vnc console token.
The default is 600 seconds (10 minutes).
You can change this value.
[consoleauth]
#
# From nova.conf
#
# /console_ token_ttl
# The lifetime of a console auth token.
#
# A console auth token is used in authorizing console access for a user.
# Once the auth token time to live count has elapsed, the token is
# considered expired. Expired tokens are then deleted.
# (integer value)
# Minimum value: 0
# Deprecated group/name - [DEFAULT]
#token_ttl = 600