yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #07706
[Bug 1255609] Re: VMware: possible collision of VNC ports
** Changed in: nova
Importance: Medium => High
** Also affects: openstack-vmwareapi-team
Importance: Undecided
Status: New
** Changed in: openstack-vmwareapi-team
Importance: Undecided => High
** Tags added: havana-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1255609
Title:
VMware: possible collision of VNC ports
Status in OpenStack Compute (Nova):
In Progress
Status in The OpenStack VMwareAPI subTeam:
New
Bug description:
We assign VNC ports to VM instances with the following method:
def _get_vnc_port(vm_ref):
"""Return VNC port for an VM."""
vm_id = int(vm_ref.value.replace('vm-', ''))
port = CONF.vmware.vnc_port + vm_id % CONF.vmware.vnc_port_total
return port
the vm_id is a simple counter in vSphere which increments fast and
there is a chance to get the same port number if the vm_ids are equal
modulo vnc_port_total (10000 by default).
A report was received that if the port number is reused you may get
access to the VNC console of another tenant. We need to fix the
implementation to always choose a port number which is not taken or
report an error if there are no free ports available.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1255609/+subscriptions