Bug 448470 - yum proxy setting incorrectly documented
yum proxy setting incorrectly documented
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum (Show other bugs)
x86_64 Linux
low Severity high
: rc
: ---
Assigned To: James Antill
Depends On:
  Show dependency treegraph
Reported: 2008-05-27 02:49 EDT by Ben.Stanley
Modified: 2009-03-25 01:41 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-25 01:41:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ben.Stanley 2008-05-27 02:49:45 EDT
Description of problem:
When attempting to configure yum to access the internet via a proxy,
by setting the variables (in accordance with the limited documentation in man
yum.conf and 
in the /etc/yum.conf file, 


I get a confusing error message:

[root@tacat etc]# yum update
Loading "changelog" plugin
Loading "installonlyn" plugin
Loading "security" plugin
Loading "rhnplugin" plugin
Loading "protectbase" plugin
Setting up Update Process
Setting up repositories
Could not retrieve mirrorlist http://apt.sw.be/redhat/el5/en/mirrors-rpmforge
error was
[Errno 4] IOError: <urlopen error nonnumeric port: '8080?'>
Error: Cannot find a valid baseurl for repo: rpmforge

To make the error message go away, simply append a '/' to the end of the proxy
setting. However, the '/' is not shown in any documentation.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configure yum.conf as described above, with no '/' on the end of the proxy
2. yum update
Actual results:
[Errno 4] IOError: <urlopen error nonnumeric port: '8080?'>

Expected results:
successful update

Additional info:
If this is the correct behaviour, please update the documentation.
Otherwise, fix it to correctly parse the port number!
Comment 1 James Antill 2009-03-25 01:41:29 EDT
 I'm pretty sure we fixed this by 3.2.8 or maybe 3.2.19

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