multiple nova-consoleauth instances cause issues with novncproxy

Bug #989337 reported by Mathew Odden on 2012-04-27
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Vish Ishaya

Bug Description

Not sure how relevant this is as I am running a packaged version of nova-consoleauth.

When you have multiple instances of nova-consoleauth running, since they hold their VNC auth tokens in a local array to that instance, the vncproxy calls to verify a token only succeeds every n-times (where n is the number of instances of nova-consoleauth you have running)

This is because the messages for auth are sent to the consoleauth services in a round robin fashion from rabbitmq, and only one of the n instances has the correct token.

The tokens should probably not be stored locally.

vishy suggested using the built-in memcache driver to store the tokens, which seems like a simple and easy fix for this.

Changed in nova:
assignee: nobody → Anthony Young (sleepsonthefloor)

Fix proposed to branch: master
Review: https://review.openstack.org/6947

Changed in nova:
status: New → In Progress
Changed in nova:
assignee: Anthony Young (sleepsonthefloor) → Vish Ishaya (vishvananda)

Reviewed: https://review.openstack.org/6947
Committed: http://github.com/openstack/nova/commit/40481581696a8ba3c056c59d97213791eca84a6c
Submitter: Jenkins
Branch: master

commit 40481581696a8ba3c056c59d97213791eca84a6c
Author: Anthony Young <email address hidden>
Date: Mon Apr 30 16:14:27 2012 -0700

    Use memcache to store consoleauth tokens

     * Rather than store tokens in a dict, use memorycache
       so that deployers can optionally use memcached if they
       would like to run multile nova-consoleauth processes
     * Fixes bug 989337

    Change-Id: I96ec4d796e53b69a494d856269e3c4e8f9b3d222

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-07-04
Changed in nova:
milestone: none → folsom-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-09-27
Changed in nova:
milestone: folsom-2 → 2012.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions