Description of problem: Can't load kickstart via HTTP Version-Release number of selected component (if applicable): 11.4.0.27-1 (rawhide 2008-01-25) How reproducible: 100% Steps to Reproduce: 1. Start install with "ksdevice=eth0 ks=http://www.mlbassoc.com/thinkpad.ks" 2. 3. Actual results: Expected results: Additional info: This same syntax worked fine with Fedora 8 (I just tested this same kickstart file using F8)
Do you have multiple network cards in your computer?
No - only one ethernet (I gave ksdevice=eth0 out of habit) I think the problem is in how the URL is parsed. The logs show something silly like trying to mount http://www.mlbassoc.com///tftpboot/thinkpad.ks
I just ran into this as well. If you keep hitting OK in the 'cannot retrieve kickstart' it will go back for DHCP again, and the install will proceed normally, Every time, the apache access logs show a successful retrieval of the file: 192.168.1.121 - - [05/Feb/2008:01:05:20 -0500] "GET /config/rawhide.cfg HTTP/1.0" 200 1102 "-" "anaconda/11.4.0.30" 192.168.1.121 - - [05/Feb/2008:01:06:04 -0500] "GET /config/rawhide.cfg HTTP/1.0" 200 1102 "-" "anaconda/11.4.0.30" 192.168.1.121 - - [05/Feb/2008:01:06:40 -0500] "GET /config/rawhide.cfg HTTP/1.0" 200 1102 "-" "anaconda/11.4.0.30" 192.168.1.121 - - [05/Feb/2008:01:06:41 -0500] "GET /config/rawhide.cfg HTTP/1.0" 200 1102 "-" "anaconda/11.4.0.30" 192.168.1.121 - - [05/Feb/2008:01:06:42 -0500] "GET /config/rawhide.cfg HTTP/1.0" 200 1102 "-" "anaconda/11.4.0.30" 192.168.1.121 - - [05/Feb/2008:01:06:43 -0500] "GET /config/rawhide.cfg HTTP/1.0" 200 1102 "-" "anaconda/11.4.0.30" 192.168.1.121 - - [05/Feb/2008:01:06:52 -0500] "GET /fedora/development/i386/os/images/updates.img HTTP/1.0" 404 325 "-" "anaconda/11.4.0.30" 192.168.1.121 - - [05/Feb/2008:01:06:52 -0500] "GET /fedora/development/i386/os/images/product.img HTTP/1.0" 404 325 "-" "anaconda/11.4.0.30" 192.168.1.121 - - [05/Feb/2008:01:06:52 -0500] "GET /fedora/development/i386/os/images/minstg2.img HTTP/1.0" 200 54345728 "-" "anaconda/11.4.0.30" The problem is *not* how the URL is parsed - obviously you can use as many slashes as you'd like in the URL and everything will be fine. Let me know if there's something more that you need me to do. Also, I changed the subject to something a little more sane and descriptive.
*** Bug 431479 has been marked as a duplicate of this bug. ***
I can reproduce this bug when running Fedora rawhide under QEMU. An interesting observation: if I pass "clock=pit" command line option to the kernel, then kickstart config file retrieval always fails. If I don't provide that option, it only fails occasionally.
F9Beta for now.
This is unlikely to make it for beta. Proposed release note: When delivering a kickstart configuration file via http, the retrieval of the file will fail, saying that the file could not be retrieved. Hitting the OK button several times without making modifications will result in the file being used. As a workaround, use one of the other supported methods to retrieve kickstart configurations.
*** Bug 432719 has been marked as a duplicate of this bug. ***
I disagree with use of the word "will" in the first sentence. This should be changed to "may", as many people here are unable to reproduce this problem. Saying "will" sets up everyone's expectation that it is going to fail, whereas that does not seem to be the case.
Where do we stand with this bug? Has it been fixed yet, do we need to retest?
Well, it seems to be working for me now - and it always failed for me before.
Same here. I'll close this tomorrow if no one has objections