Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1428242

Summary:	[Docs][RFE][VMM] A procedure outlining how to change the default serial console port must be added
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Andrew Dahms <adahms>
Component:	Documentation	Assignee:	Tahlia Richardson <trichard>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Megan Lewis <melewis>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2.3	CC:	dcadzow, lbopf, lsurette, nsednev, srevivo
Target Milestone:	ovirt-4.2.5	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	docs-accepted
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-24 06:27:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Docs	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1281283
Bug Blocks:

Description Andrew Dahms 2017-03-02 06:28:24 UTC

In Red Hat Virtualization 4.1, it is possible to change the port used for serial consoles.

The "How to change the serial console TCP port" section of the following content must be converted into a procedure and added as a section below "Opening a Serial Console to a Virtual Machine" in the Virtual Machine Management guide:

https://github.com/fromanirh/ovirt-site/blob/sercon-options/source/documentation/admin-guide/serial-console-setup.html.md

In addition to the above, the "Opening a Serial Console to a Virtual Machine" section of the same guide must also be updated to change references to port 2222 to a replaceable, and the text changed to note that 2222 is the default port, but that this port can be changed.

Comment 1 Andrew Dahms 2017-03-02 06:29:18 UTC

See also - https://gerrit.ovirt.org/#/c/57781/3/README

Comment 2 Andrew Dahms 2017-03-02 06:30:53 UTC

We should also check with engineering to see what happens when engine-setup is re-run. Will our changes be overwritten, and if we were conscientious and closed off access to 2222 in favor of our own port, will it just get re-opened? 

Based on the patch for the engineering bug, it looks like no changes have been made to engine-setup, but we should take a look and see, just to be sure.

Comment 3 Lucy Bopf 2017-09-05 13:21:25 UTC

*** Bug 1353624 has been marked as a duplicate of this bug. ***

Comment 4 Lucy Bopf 2018-01-09 00:49:47 UTC

Assigning to Billy for review.

Comment 6 Lucy Bopf 2018-06-29 04:24:40 UTC

Moving back to the rhev-docs queue to be reassigned as resources allow.

Comment 7 Lucy Bopf 2018-07-06 06:21:41 UTC

Assigning to Tahlia for review.

Comment 10 Tahlia Richardson 2018-07-24 06:27:03 UTC

Now published at https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/virtual_machine_management_guide/sect-starting_the_virtual_machine#Opening_a_Serial_Console_to_a_Virtual_Machine