VNC console does not work with VCDriver
Bug #1178369 reported by
dan wendlandt
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Critical
|
Shawn Hartsock | ||
| Grizzly |
Fix Released
|
Critical
|
Gary Kotton | ||
| VMwareAPI-Team |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
From testing, it seems like VNC consoles do not work with the VCDriver.
There are actually two issues, one a doc issue, one a code issue.
1) Doc issue:
For vSphere version 5+, you need to poke a hole in the ESX firewall to allow VNC traffic. See: http://
2) Code issue:
It seems like VNC consoles works with the ESXDriver, was not updated for the VCDriver, as get_vnc_console returns CONF.vmwareapi_
| Changed in nova: | |
| assignee: | nobody → Shawn Hartsock (hartsock) |
| Changed in nova: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in nova: | |
| importance: | Medium → High |
| Changed in nova: | |
| assignee: | Shawn Hartsock (hartsock) → Aaron Rosen (arosen) |
| Changed in nova: | |
| assignee: | Aaron Rosen (arosen) → Shawn Hartsock (hartsock) |
| Changed in nova: | |
| milestone: | none → havana-2 |
| tags: | added: grizzly-backport-potential |
| Changed in nova: | |
| status: | Fix Committed → Fix Released |
| tags: | removed: grizzly-backport-potential in-stable-grizzly |
| tags: | added: vmware-co-preferred |
| tags: | removed: vmware-co-preferred |
| Changed in openstack-vmwareapi-team: | |
| status: | New → Fix Released |
| Changed in openstack-vmwareapi-team: | |
| importance: | Undecided → Critical |
| Changed in nova: | |
| milestone: | havana-2 → 2013.2 |
To post a comment you must log in.

I'm working on a patch for this that changes the behavior of the driver for vCenter so that we end up talking to the correct IP.