Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1368237

Summary:	Insights client does not respect NO_PROXY environment variable.
Product:	Red Hat Enterprise Linux 7	Reporter:	Lindani Phiri <lphiri>
Component:	redhat-access-insights	Assignee:	Richard Brantley <rbrantle>
Status:	CLOSED ERRATA	QA Contact:	Martin Kyral <mkyral>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	7.4	CC:	chenders, cww, dkutalek, jhouska, jnewton, jucastro, mkyral, qe-baseos-apps, rbrantle, vanhoof
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:	1368236
Clones:	1435581 (view as bug list)		Environment:
Last Closed:	2017-08-01 10:09:42 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:	1368236
Bug Blocks:	1298243, 1412325, 1435581

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