Hide Forgot
Description of problem: When setting the inst..proxy directive from the kernel boot commandline, anaconda does not use it. Version-Release number of selected component (if applicable): 22AlphaTC5 How reproducible: Everytime Steps to Reproduce: 1. Type inst.repo on the cmdline. 2. Start installing behind a firewall. 3. Anaconda can not fond a mirror or installation tree. Actual results: Proxy set in UI, but not used Expected results: Anaconda should go throughout the proxy and find it's installation tree. Additional info: When inspecting the proxy settings in the ui, they show up.
I am experience thing same issue with F22 Alpha. stage2 files (squash.img and friends) and repo metadata are downloaded via the proxy but packages are not. cmdline: append initrd=initrd.img ks=ftp://ftpserver/f22_alpha_server.ks proxy=http://proxy:3128 stage2=http://mirror.pnl.gov/fedora/linux/releases/test/22_Alpha/Server/x86_64/os kickstart: url --url=http://mirror.pnl.gov/fedora/linux/releases/test/22_Alpha/Server/x86_64/os --proxy=proxy:3128 When I go into the GUI to check the settings, the proxy information is correct. It just isn't being used when downloading the packages. This worked in F21.
Looking in the anaconda source as of today (v23.4) I think the bug is in pyanaconda/packaging/dnfpayload.py in updateBaseRepo() line 705: base_ksrepo = self.data.RepoData( name=constants.BASE_REPO_NAME, baseurl=url, mirrorlist=mirrorlist, noverifyssl=not sslverify) self._add_repo(base_ksrepo) The corresponding updateBaseRepo() method line 558 in yumpayload.py passes the proxy information here: self._addYumRepo(BASE_REPO_NAME, url, mirrorlist=mirrorlist, proxyurl=proxyurl, sslverify=sslverify) I think that the proxy information is not being written to the repo file.
Ok, I made a patch and updates.img, based on anaconda-22.20.2-1 that ships with F22 Alpha, that fixes the issue where the packages in the base repo are not downloaded via the proxy. A.J., I'd be interested if this fix works for you.
Created attachment 1004991 [details] updates.img
Created attachment 1004992 [details] proxyfix.patch
With the updates.img I can install throughout a proxy. Thuis Sems to resolve the problem.
Pull request filed on github: https://github.com/rhinstaller/anaconda/pull/46
anaconda-22.20.7-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/anaconda-22.20.7-1.fc22
Package anaconda-22.20.7-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-22.20.7-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4952/anaconda-22.20.7-1.fc22 then log in and leave karma (feedback).
Package anaconda-22.20.7-1.fc22, libblockdev-0.8-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-22.20.7-1.fc22 libblockdev-0.8-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4952/libblockdev-0.8-1.fc22,anaconda-22.20.7-1.fc22 then log in and leave karma (feedback).
anaconda-22.20.7-1.fc22, libblockdev-0.8-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
In 22 Beta_RC1 I still can not use a proxy.
Created attachment 1012382 [details] Anaconda.log
Created attachment 1012383 [details] Syslog
Created attachment 1012384 [details] Packaing.log
A.J., I just tested proxy operation with Beta RC1 and it works for me. From your packaging log: > Failed to connect to mirrors.fedoraproject.org port 443: No route to host It seems like you might not have network (or internet) connectivity.
I already thought about that and checked. I do have network and nameserving functional. I tested this with a request for a local mirror. After your remark I retested with an url to dl.fedoraproject and find that proxy is working. IT looks like there is sommething wrong with the 'closest mirror' option in my test case.
Can it be, that there is something wrong with the mirrorlist mechanism behind a proxy. I see a curl error 'no route to host' and at the same time 'Ping mirroring.fedoraproject.org' resolves to an ip address. Obviously behind the proxy iT Will not ping and without proxy also curl Will fail. Looks to me that the mirror request does not use the proxy settings.
The mirror list uses https. The mirrors themselves are all http. I don't think proxy will work like you expect unless you've turned off sslverify when using the mirror.
Just tried with rawhide, and it's working fine, and going through the proxy via CONNECT. No route to host still points to a network or proxy configuration problem.