Red Hat Bugzilla – Bug 420281
Cannot find kickstart file during unattended installation
Last modified: 2008-04-07 13:02:25 EDT
Description of problem:
Using the first DVD image of Fedora 8, we tried with an actualized kickstart
file (we use kickstart in our laboratory since redhat 7.3), to make an
unattented installation of a computer.
But every attempts results in a failure, because anaconda tries to fetch from
the server a file that doesn't exists. The logs shows that it tries to fetch the
file for the same IP that the kickstart-files server has, instead of the file
that has the same IP that the DHCP server assings statically to the PC that is
If we specify manually the kickstart file, anaconda fetches the correct file,
and the kickstart process continues normally.
The IP from the NFS server is: 184.108.40.206
The IP from the PC is: 220.127.116.11 (DHCPACK with this IP)
Anaconda tries this file location:
when it should try to download the file:
Steps to Reproduce:
1. Create an DHCP+NFS configuration for kickstart
2. Host the kickstart files in the NFS server (The NFS server has no kickstart
3. Use the F8 DVD image to kickstart a PC (in the boot line from the DVD image:
linux ks text)
"Error downloading kickstart file"
"Unable to download the kickstart file...."
A normal unattented installlation.
This will be fixed in the next build of anaconda. Thanks for the detailed bug
The bug still exists in Fedora 8 Re-Spin 20080204.
I filed a bug report there:
As we use kickstart and dhcp and nfs for all our installations,
Fedora 8 is still unuseable for us.
Why where there no new boot image created without that bug?
I am wondering if nobody ist using kickstart with dhcp and nfs in this way?
anaconda doesn't get updates in between releases. This has only been fixed in
rawhide and thus isn't solved in the Fedora Unity Re-Spins. I could dig up the
commit that Chris made and see if I can backport it.
i have exactly the same problem
i can't move to f8 right now and the eol of f7 is not so far away :(
I searched the source and it think I found the patch:
Is it possible that you can apply it to anaconda-18.104.22.168-6
and include then new package in the next F8 respin?
I tried to build anaconda-22.214.171.124-6 with the patch applied and it
and has build the rpms without an error.
But I can't test the result - I'm just not sure how to build a respin
just like the release re-spins but with only the patch applied.
(I read some documents about revisor but I had not found the exactconfiguration
files for the release f8 respins (and updates-f8-yumloop.img, for example).)
Thanks in advance!
I have tested Fedora 8 Respin 20080331 and it works!
This bug is fixed and resolved in Fedora 8 Respin 20080331, many thanks!!!