Greetings,

I currently have this issue with the console and I'm not exactly sure how to troubleshoot from here. But first, let me explain the openstack setup a bit :

This is a Icehouse setup with HA through HAproxy. The load-bablanced IP for the controllers is 10.251.0.245. Here's the configuration on the compute nodes :

vnc_enabled = True
vncserver_listen = 0.0.0.0
vncserver_proxyclient_address = 10.251.0.102
novncproxy_base_url = http://10.251.0.245:6080/vnc_auto.html

Here is the configuration on the controller nodes :

vncserver_listen = 10.251.0.201
vncserver_proxyclient_address = 10.251.0.245

I have tested and I am able to access the vnc console through a realVNC client that connects directly to the compute node. However, dashboard connections always fail. Further research led me to the following line in /var/log/upstart/nova-consoleauth.log :

2015-01-27 08:57:19.976 1936 AUDIT nova.consoleauth.manager [req-dd18fb7a-e8ef-4540-b4c7-1a80a1773fc8 None None] Checking Token: -redacted-, False

(Please note I have removed the actual token number from that output)

It looks like there is something preventing the token sent by nova-compute to be recognized as true, but I am not sure how to troubleshoot it from there. How exactly is the token sent from nova-compute to nova-consoleauth? Is there a way I could intercept it and try adding it manually in nova-consoleauth, for testing purposes?