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.
Bug 1287852 - [Satellite] 6.1 installation documentation doesn't clearly list port 9090 as being required
Summary: [Satellite] 6.1 installation documentation doesn't clearly list port 9090 as ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: 6.1.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Stephen Wadeley
QA Contact: Allison Heslin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-02 20:33 UTC by Frank Hirtz
Modified: 2019-10-10 10:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-27 23:46:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Frank Hirtz 2015-12-02 20:33:40 UTC
Description of problem:

In the 6.1 Satellite documentation, if one is installing a Satellite with an integrated capsule, port 9090 needs to be available in addition to those listed in the Server install list:

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Prerequisites.html#sect-Red_Hat_Satellite-Installation_Guide-Prerequisites-Network_Ports_Required_for_Satellite_Communications

We list 9090 in table 7.1:

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Red_Hat_Satellite_Capsule_Server_Prerequisites.html#tabl-Red_Hat_Satellite-Installation_Guide-Required_Network_Ports-Satellite_to_Capsule_Communication

...but, it's not obvious that this needs to be in the port list for an integrated capsule installation and can cause installation failures. 


this is used for the foreman-proxy service, as you can see on my 6.1.4 systems both rhel6/7 its needed
<snip>
[root@satellite1 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.7 (Santiago)
[root@satellite1 ~]# hostname -f
satellite1.released-el6.satellite.lab.eng.rdu2.redhat.com
[root@satellite1 ~]# netstat -tunap | grep 9090
tcp        0      0 0.0.0.0:9090                0.0.0.0:*                   LISTEN      16491/ruby          


[root@satellite1 ~]# hostname -f
satellite1.released-el7.satellite.lab.eng.rdu2.redhat.com
[root@satellite1 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.2 (Maipo)
[root@satellite1 ~]# netstat -tunap | grep 9090
tcp        0      0 0.0.0.0:9090            0.0.0.0:*               LISTEN      24939/ruby
</snip>

I'd like to request that the documentation either make the need for the Satellite->Capsule port needing to be also opened in this configuration be made more explicit in the main section, or that 9090 be added to the main list (if that's acceptable).

Comment 1 Stephen Wadeley 2016-01-06 12:25:47 UTC
Hello

I think we should add it to the table "Ports for Client to Satellite Communication"

We have 9090 in "Ports for Client to Capsule Communication"

It says:
9090 	TCP 	HTTPS 	Sending generated SCAP reports to the proxy in the Capsule for spooling 

I believe it is also used for host discovery and provisioning by the 	discovered node. So that text should be added to the tables.

Thank you

Comment 6 Andrew Dahms 2016-02-08 05:28:09 UTC
Re-assigning to Stephen, and returning the status to VERIFIED.

Comment 8 Andrew Dahms 2016-04-27 23:46:08 UTC
This content is now live on the Customer Portal.

Closing.


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