Bug 270521 - yum does not honor per-repo proxy-setting when retrieving repodata
Summary: yum does not honor per-repo proxy-setting when retrieving repodata
Keywords:
Status: CLOSED DUPLICATE of bug 191864
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 7
Hardware: All
OS: All
medium
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F8Target
TreeView+ depends on / blocked
 
Reported: 2007-08-31 08:07 UTC by Thorsten Leemhuis
Modified: 2014-01-21 22:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-13 19:14:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Thorsten Leemhuis 2007-08-31 08:07:06 UTC
Description of problem:
At work we have a odd network setup -- we can connect via http-protocol only
over a squid proxy (e.g. outgoing via port 80 is blocked for normal systems).

No big deal as such, but I also have internal repos, which are not accessible
for the proxy. Thus I configured yum to not use the proxy for the internal repos
-- seems that is not honored when fetching metadata.

Version-Release number of selected component (if applicable):
yum-3.2.2-1.fc7

How reproducible:
Always

Additional info:

My repo-file:
---
[internal]
name=internal -- generic 
baseurl=http://foo/pub/repo/generic/$basearch/
enabled=1
proxy=_none_
metadata_expire=1
gpgcheck=0
---
# export http_proxy=http://squid.domain.de:8080
# yum update --disablerepo=* --enablerepo=internal
Setting up Update Process
http://foo/pub/repo/generic/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error
503: Server: squid/2.6.STABLE5
Date: Fri, 31 Aug 2007 08:00:48 GMT
Content-Type: text/html
Content-Length: 912
Expires: Fri, 31 Aug 2007 08:00:48 GMT
X-Squid-Error: ERR_DNS_FAIL 0
X-Cache: MISS from squid.domain.de
X-Cache-Lookup: MISS from squid.domain.de:8080
Via: 1.0 squid.domain.de:8080 (squid/2.6.STABLE5)
Proxy-Connection: close

Trying other mirror.
Error: Cannot open/read repomd.xml file for repository: internal

# unset http_proxy
# yum update --disablerepo=* --enablerepo=internal
[works as expected]

Comment 1 Thorsten Leemhuis 2007-09-01 11:45:05 UTC
(In reply to comment #0)
> Description of problem:
> At work we have a odd network setup -- we can connect via http-protocol only
> over a squid proxy (e.g. outgoing via port 80 is blocked for normal systems).

Forgot: I'm not 100% sure, but I think I ran into the similar problem with other
yum-configurations on F7 or RHEL5 before. E.g. if I have all repos apart from
one available internally I configured the proxy only for the one repo that needs
it. That failed, as yum was not able to get the mirrorlists from the server, as
it didn't use the proxy for that step. I can test this again on F7 or RHEL5 if
more details are needed. 

Comment 2 Jeremy Katz 2007-09-13 19:14:20 UTC
proxy=_none_ doesn't work right in urlgrabber..

*** This bug has been marked as a duplicate of 191864 ***


Note You need to log in before you can comment on or make changes to this bug.