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.

Document URL: 
https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-2-preparing-your-environment-for-installation


Section Number and Name: 
2.5. Ports and Firewalls Requirements

Describe the issue: 
Since Satellite 6.2 Capsules needs to be able to communicate to Satellite on port 5000/tcp

Suggestions for improvement: 
Add the required port to table Table 2.6. Ports for Capsule to Satellite Communication


Additional information: 
Additionally clients needs to communicate to Capsules/Satellite on port 5000 when pulling Docker content. Might be a good idea to add the port to table Table 2.5. Ports for Client to Capsule Communication and Table 2.4. Ports for Client to Satellite Communication

Hello


Thank you for raising this bug.

Hello Johan

This port is not listed in the matrix table for Capsule to Satellite communications. I will therefore seek confirmation from Docker SMEs. 

The port should be added to the matrix table.


Hello Partha Aji and Daniel Lobato Garcia

Can you confirm the need for TCP 5000 to be opened on Satellite and Capsule as mentioned in comment 0?


Thank you

Yes, I can confirm port 5000 is necessary in order to use the Docker registry with the default configuration.

Thank you Daniel

Hello


These changes are now live on the customer portal.

Thank you