Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Are you running more than one copy of nova-consoleauth? This will cause intermittent failures. You can get around it by only running one copy or using a memcached server to share tokens. You will need to specify the host/port of your server in memcached_servers config opt.


On Dec 11, 2012, at 10:06 AM, Jesse Pretorius wrote:

New question #216534 on OpenStack Compute (nova):

When I use ‘nova get-vnc-console test3 novnc’ to create the URL including the token for novnc access to an instance console, the novnc proxy can't connect on the first attempt. When refreshing the browser using the same URL/token it works.

In examining the logs I see that nova-consoleauth checks the token on the first attempt via rabbitmq, but I don't understand why it doesn't complete the validation properly on the first round.

Can anyone point me to a way to make this work properly the first time around using Ubuntu Precise, ideally using the standard packages? Alternatively what modifications are required to make it work?

Environment: Ubuntu Precise, Openstack Essex, multi-host

-- You received this question notification because you are a member of Nova Core, which is an answer contact for OpenStack Compute (nova).