Bug 520648
Summary: | Downloads from local RHN Satellite fail if "https_proxy" env. var. is set, even if yum is configured to use no proxy | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Frank Danapfel <fdanapfe> |
Component: | yum-rhn-plugin | Assignee: | Milan Zázrivec <mzazrivec> |
Status: | CLOSED CANTFIX | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | cperry, jhutar |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-12-17 16:07:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Frank Danapfel
2009-09-01 15:14:38 UTC
yum-rhn-plugin is -- well -- a yum plugin that in case your machine is registered to RHN / RHN Satellite adds few hooks to yum's workflow; the most important hook will make yum think there are more yum repositories to look at (channels your machine is subscribed into) when building & executing a transaction. Downloading packages from these repos (and doing the rest) is entirely yum's job. The proxy settings from /etc/sysconfig/rhn/up2date you're mentioning in the initial comment won't have any effect on how yum downloads these packages. These are in fact settings which utilities like rhn_register, rhnreg_ks, rhn_check, etc. will use when doing network connections: all the communication between client & RHN / RHN Satellite is XML-RPC and we want to support environments in which you are required to use an HTTP / HTTPS proxy of some sort to be able to connect to RHN / RHN Satellite. As far as I am concerned, yum uses urlgrabber & urllib2 when accessing a yum repository. urllib2 does honor "https_proxy" variable, though it does not honor "no_proxy". From this perspective, the problem you described is in fact expected behavior of this library. There is a patch for urllib2 which implements support for "no_proxy" [1], but this is a new thing and it definitely is not part of RHEL-5. [1] http://bugs.python.org/issue6894 Milan, thanks for the detailed explanation. If this can't be fixed in RHEL 5 is there a chance that this will be fixed in RHEL 6? The problem with urllib2 honoring "no_proxy" env. variable could be fixed (or backported) into some of the upcoming RHEL-5 update releases, as long as there will be a bug opened against python for it and it will get approved ... Though I don't maintain python package, so I can't really say for sure :) |