Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

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

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=*

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

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

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