Bug 1077855

Summary:	default of vnc_port range start seems not to be 5900, but 9100
Product:	Red Hat OpenStack	Reporter:	Jaroslav Henner <jhenner>
Component:	openstack-nova	Assignee:	Matthew Booth <mbooth>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jaroslav Henner <jhenner>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.0	CC:	ndipanov, sgordon, vpopovic, yeylon
Target Milestone:	---
Target Release:	5.0 (RHEL 7)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-23 17:58:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1055536

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.