Bug 1173335

Summary: There is not "no_proxy" filter option when using proxy.
Product: Red Hat Satellite Reporter: Harald Jensås <hjensas>
Component: Content ManagementAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0.6CC: andreas.pfaffeneder, fdewaley, meeveret, stbenjam
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-23 13:54:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Harald Jensås 2014-12-11 21:29:24 UTC
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 1 RHEL 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.

Comment 3 Stephen Benjamin 2015-04-23 13:54:01 UTC

*** This bug has been marked as a duplicate of bug 1132980 ***