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.
Description of problem:
Satellite 6 is on a network, behind a proxy. To be able to sync content from Red Hat or other external repos the Satellite will have too go trough the proxy.
There are also internal repos on the network, the proxy server cannot access these, but the Satellite itself can access them.
Version-Release number of selected component (if applicable):
How reproducible:
Reproducable
Steps to Reproduce:
1. Install Sat on network behing proxy, enable the --katello-proxy-* options.
2. Set up yum repo on another system on the repo, served via http.
3. Create a product, and a repo.
4. Add the http://<....> URL for the yum repo on the server on the internal network.
5. If the proxy cannot access the internal repo, sync will fail.
Actual results:
Sync fail because proxy cannot access the host serving the internal repo.
Expected results:
A "no_proxy" option should be available to allow configuration of domans, subnets, hosts etc that Satellite should not use the proxy to access.
Additional info:
Comment 1RHEL Program Management
2014-12-11 21:35:02 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.