Created attachment 424159 [details]
tarball of all logs from stage2
Description of problem:
If you boot with proxy=host:port anaconda will correctly download the stage2 image files using the proxy (monitor proxy logs). However the repositories that appear in package configuration screen in stage2 don't have proxy URL configured. If install proceeds no proxy will be used (monitor your proxy logs).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure a proxy host (for example with apache mod_proxy)
2. Start an install with 'linux proxy=host:port'
3. Monitoring the proxy log observe that stage2 images are downloaded via the proxy.
4. Proceed to package selection
5. Edit/Modify the repositories listed there.
No Proxy URL specified for repositories. If you leave it as is the packages will be downloaded directly not via the proxy (see your logs).
Proxy configuration is present for the repositories and packages are downloaded via proxy.
All logs will be attached. anaconda-yum.conf seems to have correct proxy definition.
Reassigning to yum. I've tracked this into the depths of anaconda and as far as I can tell everything is setup properly and yum appears to be ignoring the proxy setting in /tmp/anaconda-yum.conf
A possible complication with my setup is that my virt cannot resolve the host set for the repo, only the host for the proxy. I don't know if Alexander's setup is similar to mine or not. So if yum is expecting to resolve the repo host before using the proxy that could explain the problem.
Unless you can reproduce a problem post anaconda, I'm going to assume it's a dup of the anaconda proxy BZ.
*** This bug has been marked as a duplicate of bug 484788 ***
When adding proxy=http://host:port into yum.conf on already installed system yum used the proxy to download the packages.
It ends up the problem was anaconda's use of YumRepo objects. They don't inherit the proxy settings from the main yum.conf file so they need to be set.
Fixed in anaconda-13.21.56-1.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.