VNC console doesn't work when 'vnc_debug' flag is true
Bug #771132 reported by
Rafael Durán Castañeda
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
I don't know why, but you can't get VNC console unless you set 'vnc_debug' flag to false, I suppose this isn't the desired behavior. I almost get crazy trying to get vnc console until someone point me at this problem. You can check my answer at https:/
| Changed in nova: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
Revision history for this message
| Thierry Carrez (ttx) wrote | #1 |
| Changed in nova: | |
| importance: | High → Low |
Revision history for this message
| Mark McLoughlin (markmc) wrote | #2 |
| Changed in nova: | |
| status: | Confirmed → Fix Committed |
| Changed in nova: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is actually by design, but could use documentation or improvement.
See comment from sleepsonthefloor on the question:
"The flag vnc_debug is for protocol debugging. It bypasses authentication, and allows you to specify the vnc host and port in the url, thereby allowing you to connect to vnc consoles without asking for a token.
The vnc host and port is considered private, which is why the api doesn't return that information. Perhaps if the vnc_debug flag is set, we could embed the proper host/port info in the url so that it works by default."