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:

access denied error when expanding the Repository products:

Permission denied – connect(2) for “” port

To fix, used the line from https://access.redhat.com/solutions/1308183 :
Raw

semanage port -a -t foreman_proxy_port_t -p tcp <http_proxy_port>



Version-Release number of selected component (if applicable):
Version 6.2.8.

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Using "--katello-proxy-port=" should set up the correct SELinux context.


Additional info:

https://access.redhat.com/discussions/3008661

Bug 1177377 - Satellite 6.1 does not work with http proxy due to SELinux denials

Created redmine issue http://projects.theforeman.org/issues/19644 from this bug

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.