Bug 852768

Summary:	VNC / Spice console port range overlaps default CIM port
Product:	Red Hat Enterprise Linux 6	Reporter:	Stephen Gordon <sgordon>
Component:	ovirt-node	Assignee:	Mike Burns <mburns>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.4	CC:	acathrow, bsarathy, gouyang, huiwa, jboggs, leiwang, mburns, ovirt-maint, ycui
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-11 21:18:55 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:	839051

Description Stephen Gordon 2012-08-29 14:28:17 UTC

Description of problem:

We reserve the port range 5634 - 6166 for Spice / VNC console connections, the port used for CIM (5989) - which we are also using - falls within this range.

This is the case in both Hypervisor hosts and RHEL hosts. For Hypervisor hosts the port ranges are set in the kickstart, for RHEL hosts they come from the rhevm-config options sent to vdsm-bootstrap.
  
Actual results:

VNC / Spice console port range overlaps default CIM port

Expected results:

We should not use, or potentially use, one port for more than one purpose.

Comment 1 Mike Burns 2012-09-07 12:00:23 UTC

Bhavna/Andy,

Any thoughts on this?  

We could modify the cim server to run on a non-standard port or allow the port to be configurable, but I think this is just the first case of us colliding with the port range set aside for Spice/VNC.  Perhaps it's time to revisit this block of ports?

Comment 4 Andrew Cathrow 2013-07-11 21:18:55 UTC

This is already handled by the port detection mechanism