novnc no longer sets token inside cookie
Bug #1822676 reported by
Mohammed Naser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Mohammed Naser | ||
Rocky |
Fix Committed
|
Undecided
|
Unassigned | ||
Stein |
Fix Committed
|
Medium
|
Lee Yarwood | ||
OpenStack-Ansible |
Fix Released
|
Undecided
|
melanie witt |
Bug Description
For a long time, noVNC set the token inside a cookie so that when the /websockify request came in, we had it in the cookies and we could look it up from there and return the correct host.
However, since the following commit, they've removed this behavior
This means that we're unable to use latest noVNC with Nova. There is a really gross workaround of using the 'path' override in the URL for something like this
http://
That feels pretty lame to me and it will have all deployment tools change their settings. Also, this wasn't caught in CI because we deploy novnc from packages.
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
assignee: | melanie witt (melwitt) → Mohammed Naser (mnaser) |
Changed in openstack-ansible: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
I'm investigating a fix for this in nova.