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.

Description of problem:
firewall rules need to allow incoming TCP connections to port 5647. qdrouterd listens there and e.g. content hosts running goferd needs to connect there.


Version-Release number of selected component (if applicable):
Sat 6.1. RC5


How reproducible:
100%


Steps to Reproduce:
1. Have firewall per install manual (port 5647 is not mentioned there)
2. Have content host with katello-agent installed
3. Check in /var/log/messages that goferd fails to connect to the satellite that port


Actual results:


Expected results:


Additional info:

Forgot to mention: both ports 5647 and 5646 need to be allowed in Satellite and also in external capsules.

Raising blocker? as not having this in docs would have severe impact to production, including inability to apply an errata to a content host.

Please also mention adding the two new ports to _upgrade_ guide, as Sat6.0 does not have this requirement.

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.