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 1194066 - Port 5000 TCP should be exposed on firewall or iptables in order to pull docker images from Satellite
Summary: Port 5000 TCP should be exposed on firewall or iptables in order to pull dock...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Peter Ondrejka
QA Contact: David O'Brien
URL:
Whiteboard:
Depends On:
Blocks: 1190289
TreeView+ depends on / blocked
 
Reported: 2015-02-18 22:39 UTC by Elyézer Rezende
Modified: 2019-09-25 20:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-27 08:14:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Elyézer Rezende 2015-02-18 22:39:31 UTC 
Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 
Add a section with required firewalld or iptables rules to expose port 5000 TCP. This is needed in order to pull docker images from the Satellite server.

Additional information: 
I have not checked if is possible to change the port used by Satellite for the docker registry, but the 5000 is the one used currently.
Comment 1 Athene Chan 2015-02-19 03:42:55 UTC 
Hi Elyezer,

Thanks for the feedback! Will the port be used by any other service? The reason I am asking is, I am wondering if it would be better to add this to the prerequisites in the Docker subsection instead?

Thank you,
Athene
Comment 2 Partha Aji 2015-03-05 19:43:58 UTC 
For satellite6 I think its fair to assume the docker content will be exposed only on port 5000. During the docker pull satellite does make the assumption that the customer will be using 5000 (hardcoded as of now.)
Comment 3 Athene Chan 2015-03-06 05:31:41 UTC 
Thanks Partha!!
Comment 4 Athene Chan 2015-04-03 06:26:37 UTC 
Hi Peter,

I am assigning this to you to add in as a prerequisite in the Docker section. Since the port is only used by Docker, it would be best to add this firewall prerequisite in the correct section.

Let me know if you have questions!

Cheers,
Athene
Comment 5 RHEL Program Management 2015-04-21 16:06:17 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 6 Elyézer Rezende 2015-05-04 13:06:49 UTC 
As Partha said, this is a docker specific prerequisite.
Comment 8 David O'Brien 2015-05-25 03:58:36 UTC 
Verified that "Make sure the port 5000 is enabled on the Satellite server." exists in the appropriate place.

I think the previous procedure Procedure 8.1. To Prepare a Container Host: would benefit from a minor change:

Step 3.a) actually contains three steps. I think they should be separated.

a) If the container host is on the same machine as the Satellite server...

b)  Modify the OPTIONS variable in the /etc/sysconfig/docker file as follows: 

c)  Restart the affected services to apply the changes: 

If you make that small change just move this to verified.

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