Bug 250209
Summary: | Yum proxy settings ignored when EPEL repo is installed | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | tony <tony1> |
Component: | yum | Assignee: | James Antill <james.antill> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.0 | CC: | kevin, tim.lauridsen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-25 06:18:46 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
tony
2007-07-31 01:51:43 UTC
As far as I know yum doesn't have any way of reading the proxy settings that are set in up2date. :( Does yum work natively to download your RHEL channels with the correct proxy without having the epel repository enabled? This seems like an issue with the RHEL yum not being able to read those proxy settings from up2date. yum reads it's proxy info. from /etc/yum.conf ... however when using yum with yum-rhn-plugin, the RHN part takes over file downloads (due to the complexity of RHN interaction) and that uses the proxy info. in the up2date dir. |