Bug 1717961 - RFE: Spacewalk behind a Proxy should use no_proxy
Summary: RFE: Spacewalk behind a Proxy should use no_proxy
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.9
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: spacewalk-rfe
TreeView+ depends on / blocked
 
Reported: 2019-06-06 14:23 UTC by Jan Meerkamp
Modified: 2020-03-24 13:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-24 13:22:38 UTC
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.