Description of problem:
When using a HTTP kickstart install on X86_64 systems, a possible race
condition prevents anaconda from realizing it has successfully found a
file on th eweb server.
Version-Release number of selected component (if applicable):
RHEL WS 3 U3
Steps to Reproduce:
1. Set up a kickstart install that points to a URL for a kickstart file
2. Enter valid IP information (not using DHCP)
3. Anaconda will seem to fail retrieving kickstart file
Anaconda reports that it fails to find the kickstart configuration
file, but the web server reports a success code to the query (200):
<ip_address> - - [10/Nov/2004:15:25:07 -0700] "GET
HTTP/1.1" 200 3538 "-" "Mozilla/5.0 (X11; U; Linux i686; en-US;
Notice the success code in the above log snippet (200).
Should acknowledge successful retrieval, and use the file
Works on i386 fine. Also fails when the ks.cfg is on the CDROM and
points to a URL installation directory. Will fail to find
"netstg2.img", even though the server reports a success code. Also,
in this instance, when anaconda fails back to the user and prompts the
user for hostname/path information, you can leave the default info
(the info it used in the first place), and it will retrieve
Which updat erelease is this? What network adapter and static or dhcp?
This is RHEL WS3 Update 3. It is using the tg3 network driver, and
using static IP. Here is the isolinux.cfg label info for this
append initrd=initws3.x64 \
<the append... line is one line, broken up for readability>
Since I'm not sending it any IP info via anaconda, it does a DHCP
broadcase, fails that, and prompts the user for IP information (which
is what I want it to do). I enter the IP information, and that's when
it fails retrieving the kickstart file (which is dynamically created).
Could you try the U4 beta and see if it works better? There are some
changes there explicitly to help with weird link negotiation situations.
Hmm.. I will give it a shot. Thanks.
Seems to be working in RHEL WS 4 Beta 2, thanks! Is there any chance
of backporting these fixes into the next update for RHEL 3?
Crap.. misread your request earlier- you wanted me to test the U4
beta, and I tested the RHEL 4 beta... <grumble> I will try again with
the U4 beta, as well.
U4 beta should have identical changes to RHEL4 beta2, so that's a
promising sign :)
OK- testing fine with WS3 U4 on X86-64. I look forward to the
production release- thanks for helping me with this!
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed). If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.