Bug 1190197

Summary: [RFE] katello-installer option to exclude the proxy use for a domain or url
Product: Red Hat Satellite Reporter: Johan Swensson <jswensso>
Component: InstallationAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.7CC: bkearney, ddevra, katello-bugs, ktordeur, xdmoon
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-12 14:59: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 Johan Swensson 2015-02-06 15:52:03 UTC 
Description of problem:
If one configures Satellite 6 to use a proxy to access Red Hat cdn the ability to sync 3rd party repos hosted internally is lost.

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

How reproducible:
100%

Steps to Reproduce:
1. Run katello-installer with the options --katello-proxy-url and --katello-proxy-port specifying your proxy
2. Create a new product
3. Create a repository with a url to a internal repository, for example: http://reposerver.acme.com/puppet-modules
4. Try sync the repository


Actual results:
Satellite tries to sync the repository through the proxy.

Expected results:
Satellite should be able to exlude the proxy usage on some urls.

Additional info:
pulp-puppet-module-builder can be used to create the repository as described in https://access.redhat.com/articles/1169613
Comment 1 RHEL Program Management 2015-02-06 15:53:18 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 7 Red Hat Bugzilla 2023-09-14 02:54:31 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days