Bug 1526578

Summary:	[RFE] Add option in Satellite to bypass proxy when adding private local repositories
Product:	Red Hat Satellite	Reporter:	patalber
Component:	Repositories	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.13	CC:	bkearney, jsherril
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-23 18:48:07 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 patalber 2017-12-15 19:08:07 UTC

Description of problem:
Per client: "I have a repo on my local network and I want to include it in Satellite. The problem is that in order to do that I must configure a squid. Can you please include an option to bypass the proxy configured in Satellite?"

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


How reproducible: 100% (on client's local network)


Steps to Reproduce:
1. Create a repository for a private repo on a local network
2. Attempt to synchronize without extra configuration
3. 

Actual results:
The client must configure a squid to allow the repository on his network to sync with Satellite.

Expected results:
The repository on his network will sync with Satellite by default with no extra configuration outside of Satellite needed.

Additional info:

Comment 1 Justin Sherrill 2018-03-23 18:48:07 UTC


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