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.
Description of problem:
* The subscription-manager yum plugin fails to honor both the $http(s)_proxy environment variables and the /etc/yum.conf proxy directive.
* The subscription-manager command line tool fails to honor the $http(s)_proxy environment vaiables (requiring either rhsm.conf to be updated or --proxy to be specified)
Version-Release number of selected component (if applicable):
1.10.6-1.el7
How reproducible:
Always
Steps to Reproduce:
1. Be on a network requiring the use of an http proxy
2. Configure http(s)_proxy in /etc/environment, or /etc/yum.conf
3. Run "yum check-update" or "yum list available" etc
Actual results:
[root@el7b1 ~]# yum check-update
Loaded plugins: langpacks, product-id, subscription-manager
[Errno 111] Connection refused
Expected results:
* If a proxy is not configured in /etc/rhsm/rhsm.conf the yum plugin should use whatever configuration mechanism(s) that yum uses to determine the proxy.
* I think it probably also makes sense for the subscription-manager command to honour the $http(s)_proxy environment variables
[root@el7b1 ~]# yum check-update
Loaded plugins: langpacks, product-id, subscription-manager
This system is receiving updates from Red Hat Subscription Management.
rhel-7-public-beta-rpms | 3.4 kB 00:00:00
Comment 2RHEL Program Management
2014-04-15 05:47:35 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 4Jesus M. Rodriguez
2014-10-01 00:13:44 UTC
This was fixed in subscription-manager 1.10.14-7. Please upgrade the subscription-manager and python-rhsm packages.