Bug 1368237 - Insights client does not respect NO_PROXY environment variable.
Summary: Insights client does not respect NO_PROXY environment variable.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: redhat-access-insights
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: rc
: ---
Assignee: Richard Brantley
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On: 1368236
Blocks: 1298243 1412325 1435581
TreeView+ depends on / blocked
 
Reported: 2016-08-18 18:45 UTC by Lindani Phiri
Modified: 2020-09-10 09:44 UTC (History)
10 users (show)

Fixed In Version: redhat-access-insights-1.0.13-2
Doc Type: If docs needed, set a value
Doc Text:
When a proxy was set up with a HTTPS_PROXY environment variable, but the NO_PROXY environment variable was also configured on the system and included an exception for Red Hat servers, the Insights client ignored the NO_PROXY variable. As a consequence, the client attempted to connect to the servers using the proxy, and the registration failed. With this update, the Insights client respects the NO_PROXY variable, and the described problem no longer occurs.
Clone Of: 1368236
: 1435581 (view as bug list)
Environment:
Last Closed: 2017-08-01 10:09:42 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2324 0 normal SHIPPED_LIVE redhat-access-insights bug fix update 2017-08-01 12:44:46 UTC

Description Lindani Phiri 2016-08-18 18:45:49 UTC 
+++ This bug was initially created as a clone of Bug #1368236 +++

Description of problem:

When both the HTTP(S)_PROXY  and NO_PROXY environment variables are set,
the Insights client attempts to connect via the http proxy, even when the Insights destination url is in the NO_PROXY list.

Please see linked customer case for concrete scenario/example.


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

How reproducible:
Always


Steps to Reproduce:
1. Configure HTTPS_PROXY and NON_PROXY environment variables in a shell adding "cert-api.access.redhat.com" to the no proxy list
2. Attempt insights client registration
3. Monitor proxy server logs

Actual results:

Insights client connects to "cert-api.access.redhat.com" via the proxy set in HTTPS_PROXY variable

Expected results:

Insights client connects directly to "cert-api.access.redhat.com", without connecting proxy.
Comment 4 Jan Houska 2017-03-23 16:47:32 UTC 
Yes I can. qa-ack+ set
Comment 13 errata-xmlrpc 2017-08-01 10:09:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2324
Note You need to log in before you can comment on or make changes to this bug.