Bug 1069430 - VMware: fix the VNC port allocation
Summary: VMware: fix the VNC port allocation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 5.0 (RHEL 7)
Assignee: Matthew Booth
QA Contact: Jaroslav Henner
URL:
Whiteboard:
Depends On:
Blocks: 1055536 1077017
TreeView+ depends on / blocked
 
Reported: 2014-02-25 02:18 UTC by Tracy Jones
Modified: 2019-09-09 15:16 UTC (History)
7 users (show)

Fixed In Version: openstack-nova-2014.1-3.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, instances running on a VMware host were allocated a VNC port in a manner which was not guaranteed to be unique. This meant it was possible for multiple instances to be given the same VNC port on the same VMware host. Accessing the console of any of these instances would give access to one of them, but which one was non-deterministic. With this update, the VNC port allocated is now guaranteed to be unique in a vCenter, and it is no longer possible to have a VNC port collision between two guests.
Clone Of:
: 1077017 (view as bug list)
Environment:
Last Closed: 2014-07-08 15:28:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 58994 0 None None None Never
Red Hat Bugzilla 1077855 0 unspecified CLOSED default of vnc_port range start seems not to be 5900, but 9100 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHEA-2014:0853 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement - Compute 2014-07-08 19:22:38 UTC

Internal Links: 1077855

Description Tracy Jones 2014-02-25 02:18:15 UTC 
https://review.openstack.org/#/c/58994
Comment 2 Stephen Gordon 2014-05-27 14:35:20 UTC 
Hi Jaroslav,

Did Bug # 1077017 fix this in Havana - can we close this string of bugs?

Thanks,

Steve
Comment 3 Stephen Gordon 2014-06-04 12:29:40 UTC 
Confirmed with Matt this was in Icehouse.
Comment 4 Jaroslav Henner 2014-06-13 19:29:02 UTC 
~ # grep RemoteDisplay.vnc.port /vmfs/volumes/6a6da14b-0ce58e38/3b322e49-9e63-4932-93ce-80fba4aa
9e96/3b322e49-9e63-4932-93ce-80fba4aa9e96.vmx
RemoteDisplay.vnc.port = "5906"

It looks like the starting vnc port is 5900, as configured in nova.conf.
Comment 8 errata-xmlrpc 2014-07-08 15:28:16 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0853.html
Note You need to log in before you can comment on or make changes to this bug.