RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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?

This is already handled by the port detection mechanism