Description of problem: Fedora 13 network installation disc Fedora-13-Alpha-i386-netinst.iso cannot retrieve repository metadata by using a proxy configuration. The same thing was happening to fedora 12 as well. Note that the test was conducted through a virtual machine. Version-Release number of selected component (if applicable): 13.32 How reproducible: Run the installer through vmplayer and when it comes to the step that asks for the repositories, it produces an error. Editing the popup to enter your proxy configuration it still doesn't make any difference. I have also changed the protocol of the repository address from HTTPS to HTTP to no avail. Steps to Reproduce: 1. Create new vmware Fedora 12 installation 2. Use Fedora-13-Alpha-i386-netinst.iso as the installation source 3. Proceed the installation up to repository configuration Actual results: The following error occurs: Unable to read package metadata from repository. This may be due to a missing repodata directory. Please ensure that your repository has been correctly generated. Cannot retrieve repository metadata (repomd.xml) for repository: UIEdited_11. Please verify its path and try again. Expected results: The proxy configuration should have worked. Additional info: The same thing was happening with the F12 net installation disc at VirtualBox as well. Now the installation of F13 on a VirtualBox does not start at all. The kernel hangs, before entering anaconda graphical installation.
Screenshot of the error: http://img707.imageshack.us/img707/5005/fedora13alphaproxy.jpg
Radek - I wonder if this has anything to do with the repo editor UI work you've been doing. I don't think there's much more complicated than setting the proxy values on the repo object.
Could you please collect and attach /tmp/yum.log and /tmp/anaconda.log after failing repo editing dialogs appear? You can do it from shell by switching to tty2 (ctrl-alt-f2) and copying to local storage or with scp. Also it might be helpful to see if your proxy configuration works when you set it on boot command line by adding parameter: proxy=http://squid.eurodyn.com:8080
Created attachment 400171 [details] Fedora 13 alpha /tmp contents I've included the whole /tmp contents for further investigation just after I have tried twice to enter proxy configuration and download the repomd.xml either as HTTPS or HTTP mirror list URL.
Created attachment 400236 [details] Kernel proxy boot option Booting the installation disc with the suggested proxy boot option produced the attached error.
Created attachment 400237 [details] Command line proxy configuration Proof that my proxy works fine. On the installation disc I have pressed ctrl-alt-f2 to access the command prompt. I have done an example without setting any proxy by using wget command that fails, and then I've set up a proxy and run the command again. The command was successful.
Thanks for the logs and additional information, does appending updates=http://rvykydal.fedorapeople.org/updates.proxy.img help? (Well, I'm not sure if anaconda will be able to download it from this url with your network/proxy configuration, perhaps you can download it somewhere on your local network and change the url in updates parameter above accordingly) It is an image containing a fix (http://fedoraproject.org/wiki/Anaconda/Updates)
Created attachment 400425 [details] Kernel updates boot option /tmp contents Hello, I've tried your suggestion without success. I've included all the contents of /tmp for further investigation. There you can also find the wget-test-by-panos.log with the test of wget command from installation disc's command prompt.
Hi, thanks for retesting, I've noticed that your wget test is using default proxy port 80 in comment #6, and no proxy at all in comment #8, while on your screenshot from comment #1 you are using port 8080. I wonder if you did use the port 80 when setting the proxy in UI dialog in test from comment #8 (from the log it seems, you didn't set it at all in the dialog) - value "http://squid.eurodyn.com:80" should work, even without ":80" port specification probably.
Created attachment 400453 [details] Proxy configuration solved (/tmp contents) I apologise for the inconvenience. The correct proxy port is 8080 and not 80. My comment #6 seems to have downloaded the proxy server's index page and not the requested URL's page. For comment #8 indeed I haven't set any proxy configuration, because I was confused by the errors to mount the updates as loop device and the updates.proxy.img had zero size and I didn't proceed the installation. I have tried again and it failed to download the repo data. By changing the URL of the mirror site from HTTPS to HTTP and it worked fine! I attach the logs again just after the installation had finished and the reboot was requested. Do you have any idea why it fails with the HTTPS version of the mirror site? The same happens to yum and I have to drop HTTPS from the mirror URL in /etc/yum.repos.d/fedora.repo in order yum to work and retrieve the repomd.xml.
(In reply to comment #10) > Do you have any idea why it fails with the HTTPS version of the mirror site? > The same happens to yum and I have to drop HTTPS from the mirror URL in > /etc/yum.repos.d/fedora.repo in order yum to work and retrieve the repomd.xml. Maybe your proxy is not configured for https access. If it is, you may need to configure anaconda or yum to use https proxy (e.g. use "https://squid..." as proxy option in anaconda, or set https_proxy="https://squid..." for curl or wget).
Ah yes! The following: setenv https_proxy http://squid... did the trick for yum and now I can use HTTPS for the mirrorlist. Although it seems overkill to use encryption to get a publicly available mirror list. I tried again the installer and produced an error the first time I supplied the proxy configuration. The second time it worked even with the HTTPS mirrorlist. The problem why it is failing the first time might have been catched in my last logs. Anyway, that might be another problem and if you cannot reproduce it, I'm at your disposal for any further information. Thank you very much for your prompt resolution on this problem.
Thanks for the report. This should be fixed in version 14.2-1 of anaconda.
This bug affects Fedora 12 netinstall too. Filling the form to define a proxy doesn't work. I tried your updated img with Fedora 12 installer without success since it fails to a black screen after fetching the update. Is there a way to achieve a network install with the Fedora 12 netinst iso ? Should I fill an other bug report ?
I tried the proxy boot option described @ http://fedoraproject.org/wiki/Anaconda/Options too, and by using both http and https repository.
(In reply to comment #14) > This bug affects Fedora 12 netinstall too. Filling the form to define a proxy > doesn't work. I tried your updated img with Fedora 12 installer without success > since it fails to a black screen after fetching the update. Is there a way to > achieve a network install with the Fedora 12 netinst iso ? Should I fill an > other bug report ? If your issue is the same as this bug, and it seems that it is, there is no point in opening new bug for f12 as it will be closed as duplicate of this one which is fixed in rawhide (and will go to Fedora 14) - we can't fix anaconda for F12 now. Proxy boot option should be fixed in Fedora 13. The only thing I can do for you is to create this updates image http://rvykydal.fedorapeople.org/updates.f12proxy.img with patch from this bug applied to anaconda from F12. Also a workaround might work - using user name and password in repo editing dialog - but that would probably also require configuration of your proxy.
Thanks you for this "backport". This image works well. The wizard uses the defined proxy (in the form) for fetching the mirrors list, then a popup appears, repeating the same error message that the one describe in this bug report. I filled the form one more time and continued the download of the repo data, which achieved without problem. Thanks again for your help !
(In reply to comment #17) > Thanks again for your help ! No problem, good to hear and know that it works.
*** Bug 580756 has been marked as a duplicate of this bug. ***
This fix went also in f13, should apperar in version 13.38-1 of anaconda. Clear description of the bug is in duplicate bug #580756.
Can someone confirm this is fixed in TC1? http://serverbeach1.fedoraproject.org/pub/alt/stage/13.TC1/ -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Looks good to me. Passed proxy=http://proxy.home:3128 on the kernel command line and it was propagated to the GUI repo properly.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping