NoVNC KeyError on connect
Bug #1030383 reported by
gh
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| devstack |
Invalid
|
High
|
Anthony Young | ||
Bug Description
Using source from github repo as of 2012-07-28.
I am getting the following error when I attempt to login to my NoVNC server via Google Chrome:
2: 192.158.1.50: new handler Process
2: 192.158.1.50: Plain non-SSL (ws://) WebSocket connection
2: 192.158.1.50: Version hybi-13, base64: 'True'
2: 192.158.1.50: Path: '/websockify'
2: handler exception: 'token'
2: Traceback (most recent call last):
File "/opt/stack/
self.
File "./utils/
token = cookie[
KeyError: 'token'
Revision history for this message
| Anthony Young (sleepsonthefloor) wrote | #1 |
| affects: | nova → devstack |
| Changed in devstack: | |
| assignee: | nobody → Anthony Young (sleepsonthefloor) |
| importance: | Undecided → High |
| Changed in devstack: | |
| status: | New → In Progress |
| Changed in devstack: | |
| status: | In Progress → Invalid |
To post a comment you must log in.
For Folsom, nova-novncproxy ships with nova - this makes things much easier for packagers. I believe that the nova version of nova-novncproxy is working properly, but we need to update devstack to demonstrate this new configuration.
If you are still able to reproduce this issue with the revised configuration, we can target this back to nova. Thanks for reporting this.