Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionStephen Wadeley
2015-12-08 12:27:13 UTC
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Managing_Hypervisors_and_Virtual_Guest_Subscriptions-Setting_up_a_VMware_Hypervisor.html
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:
https://access.redhat.com/discussions/1987953#comment-994153