Bug 1717961

Summary:	RFE: Spacewalk behind a Proxy should use no_proxy
Product:	[Community] Spacewalk	Reporter:	Jan Meerkamp <meerkamp>
Component:	Server	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED DEFERRED	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	2.9	CC:	mmraka
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-24 13:22:38 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:
Bug Depends On:
Bug Blocks:	737830

Description Jan Meerkamp 2019-06-06 14:23:49 UTC

Description of problem:

Spacewalk does not use no_proxy env and it is not picked up when set in rhn.conf

server.satellite.no_proxy = internal.loc,192.168.11.6

How reproducible:

Setup a Spacewalk Server behind a proxy and have a Internal Repository

Actual results:
Either Proxy is set and the External Repos gets synced or Proxy is not set and only the internal Repo is Synced


Expected results:
Without reconfiguration internal and external Resources are available.

Comment 1 Michael Mráka 2020-03-24 13:22:38 UTC

Spacewalk project as an upstream for Red Hat Satellite 5 product is going to be End Of Life on May 31 2020.

Spacewalk 2.10 has been released as the last release of this project.
https://github.com/spacewalkproject/spacewalk/wiki/ReleaseNotes210

Any new feature will not be included therefore closing remaining RFEs to set expectations properly.