Bug 1658265

Summary:	[RFE] virt-who-configure-plugin should set 'NO_PROXY=*' by default.
Product:	Red Hat Satellite	Reporter:	Rich Jerrido <rjerrido>
Component:	Virt-who Configure Plugin	Assignee:	Marek Hulan <mhulan>
Status:	CLOSED ERRATA	QA Contact:	Kunxin Huang <kuhuang>
Severity:	medium	Docs Contact:	satellite-doc-list
Priority:	unspecified
Version:	6.4.0	CC:	mhulan, spetrosi
Target Milestone:	6.6.0	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Previously, if you had an HTTP proxy configured in Satellite, the virt-who configuration attempted to use the HTTP proxy to submit virt-who data and failed. With this release, virt-who ignores the HTTP proxy setting and submits data to Satellite directly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 12:47:06 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 Rich Jerrido 2018-12-11 16:18:27 UTC

Description of problem:

Many customers configure their Satellites to reach the CDN via an HTTP Proxy. 
By default, we guide the customers to install virt-who on the Satellite server. As such, the virt-who configuration will attempt to use the configured HTTP proxy to submit virt-who data and will fail. 

As it is rare that the HTTP proxy allows this connection and as such, we request that we set 'NO_PROXY=*' in /etc/sysconfig/virt-who

Comment 4 Rich Jerrido 2018-12-11 16:24:13 UTC

Note: the virt-who wizard allows you not to set a proxy, but when no proxy is configured in the plugin, virt-who defaults to using the same proxy as RHSM / subscription-manager. 

To TRULY set no proxy (either implicit or explicit), we need to set NO_PROXY=*

Comment 5 Marek Hulan 2018-12-20 20:05:15 UTC

Created redmine issue https://projects.theforeman.org/issues/25746 from this bug

Comment 6 Satellite Program 2018-12-21 15:04:01 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25746 has been resolved.

Comment 10 errata-xmlrpc 2019-10-22 12:47:06 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/RHSA-2019:3172