Bug 1077855 - default of vnc_port range start seems not to be 5900, but 9100
Summary: default of vnc_port range start seems not to be 5900, but 9100
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 3.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Matthew Booth
QA Contact: Jaroslav Henner
URL:
Whiteboard:
Depends On:
Blocks: 1055536
TreeView+ depends on / blocked
 
Reported: 2014-03-18 17:34 UTC by Jaroslav Henner
Modified: 2019-09-09 13:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-23 17:58:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1294238 0 None None None Never
Red Hat Bugzilla 1069430 0 high CLOSED VMware: fix the VNC port allocation 2021-02-22 00:41:40 UTC

Internal Links: 1069430

Description Jaroslav Henner 2014-03-18 17:34:13 UTC 
Description of problem:
In the nova conf, there is:

# VNC starting port (integer value)
#vnc_port=5900

Which means the default value is 5900, but it is not so. with this configuration, vmware VMs seems to have ports >=9100

Version-Release number of selected component (if applicable):
openstack-nova-compute-2013.2.2-2.el6ost.noarch

How reproducible:


Steps to Reproduce:
1. make sure the vnc_port under vmware is unset
2. restart nova-compute
3. boot the VM
4. On the ESXi:

~ # grep vnc /vmfs/volumes/shared/1f9f6326-18bd-4972-8a59-5c268dc28b53/*.vmx
RemoteDisplay.vnc.enabled = "true"
RemoteDisplay.vnc.port = "9129"

5. openstack-config --set /etc/nova/nova.conf vmware vnc_port 5900
6. restart, boot, check:


~ # grep vnc /vmfs/volumes/shared/xxxx-yyy-.../*.vmx
RemoteDisplay.vnc.enabled = "true"
RemoteDisplay.vnc.port = "59xx"


Actual results:
default is something else then it was meant to be

Expected results:
default is what is meant to be


Additional info:
Comment 2 Jaroslav Henner 2014-03-18 18:24:48 UTC 
This may get fixed together with #1069430
Comment 4 Jaroslav Henner 2014-04-17 13:04:02 UTC 
BZ#1077017 (A clone of BZ#1069430) seems to have fixed this in Havana
Comment 5 Stephen Gordon 2014-05-23 17:58:24 UTC 
If it's fixed in Havana, and it's in master for Icehouse, I don't think we have anything further to do here.
Note You need to log in before you can comment on or make changes to this bug.