multiple nova-consoleauth instances cause issues with novncproxy
Bug #989337 reported by
Mathew Odden
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
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.
Changed in nova: | |
assignee: | Anthony Young (sleepsonthefloor) → Vish Ishaya (vishvananda) |
Changed in nova: | |
milestone: | none → folsom-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | folsom-2 → 2012.2 |
To post a comment you must log in.
vishy suggested using the built-in memcache driver to store the tokens, which seems like a simple and easy fix for this.