Bug 1289556 - Firewall commands in virt-who section are incorrect
Firewall commands in virt-who section are incorrect
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Docs Install Guide (Show other bugs)
Unspecified Unspecified
medium Severity medium (vote)
: Beta
: 6.2
Assigned To: Byron Gravenorst
Stephen Wadeley
: Documentation
Depends On:
  Show dependency treegraph
Reported: 2015-12-08 07:27 EST by Stephen Wadeley
Modified: 2016-04-27 20:08 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-04-27 20:08:56 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stephen Wadeley 2015-12-08 07:27:13 EST
Document URL: 


Section Number and Name: 

Describe the issue: 

This para is incorrect:

The system running virt-who requires open access to vCenter on ports 80 and 443. Before following these steps, create a firewall exception to allow connections on port 80 and 443 from the Red Hat Satellite server to the vCenter: 

The system that needs access to vCenter on ports 80/443 is the RHEL VM running virt-who, so connectivity is from the RHEL VM to the vCenter server (this RHEL VM may be the Satellite server).

 Directly under this paragraph the documentation provides firewall rules for the RHEL VM (that is running virt-who) that are inbound for new connections, this is in the incorrect direction.. the vCenter doesn't initiate new connections to the RHEL VM. 

From the above paragraph "from the Red Hat Satellite server to the vCenter", this isn't completely correct. It is the RHEL VM that is running virt-who that needs access to the vCenter on 80 and 443, not the Satellite server. The Satellite server may be running virt-who, but this isn't the scenario described in the documentation. If virt-who is running on a different guest (commonly described configuration), Satellite doesn't interact with vCenter directly. 

Suggestions for improvement: 

Make it clear that the ports need to be opened on the base system running vCenter.

Additional information: 

As reported here:
Comment 1 Andrew Dahms 2015-12-08 19:38:58 EST
Assigning to Byron for review.
Comment 3 Andrew Dahms 2016-04-27 20:08:56 EDT
This content is now live on the Customer Portal.


Note You need to log in before you can comment on or make changes to this bug.