Red Hat Bugzilla – Bug 487503
anaconda in F10 & F11 gets ok the kickstart network config, but stops and asks anyway
Last modified: 2010-02-17 14:47:33 EST
Description of problem:
Even if network parameters (dhcp) is specified in the kickstart file, the automated installation stops and asks for the network parameters.
I tried to set something like ip=10.11.12.13 and it is correctly shown, meaning that it is taken into account, but the installer stops anyway in the network configuration screen.
I tried with and without autostep.
I tried with and without ksdevice as linux kernel parameter.
The kickstart file specifies ks=floppy:/ks.cfg and the floppy ks.cfg specifies a repository in an ftp server.
The same kickstart file works fine in F9, meaning that it takes the network parameter (dhcp) and goes all the way through installation without stopping in the network screen.
The idea of this automatic installation is to install virtual machines, and user intervention is not permitted during installation.
Version-Release number of selected component (if applicable):
The version of fedora is 10. The version of anaconda is the anaconda that comes with the install DVD, which I think it is 184.108.40.206 or .63, I am not sure.
Easy to reproduce. Here I put the ks.cfg file I am using:
url --url ftp://172.16.120.1/root/vm/tmp/image
network --device eth0 --onboot yes --bootproto dhcp --hostname caca
#with or without autostep doesn't make any difference
authconfig --enableshadow --enablemd5
bootloader --location=mbr --append="rhgb quiet"
clearpart --all --initlabel
part / --fstype ext3 --size=10 --grow
part swap --size=512
%packages --nobase --ignoremissing
Steps to Reproduce:
1. just create a floppy with a similar ks.cfg with a proper ftp repository.
2. boot an f10 cd or dvd (like netinst cd)
3. ....and before booting, add ks=floppy:/ks.cfg
Installs takes in account everything, even network, but instead of skipping the network config screen, it stops.
I am expecting not to stop during the entire installation, which is what happens with this same ks.cfg file using Fedora 9.
Is this still a problem in rawhide?
(In reply to comment #1)
> Is this still a problem in rawhide?
Yes it is still there......at least when you arrive to that screen....which is not always the case due to some randoms SIGABRT that happen before that step.
Patches are waiting for review.
I've just tried those modifications on the original stage2.img from the fc10 DVD, mounting it, patching it. remaking it with mkfs.cramfs, and putting it back into the DVD, and the bug is still present. The installer still stops in the network configuration screen (the installation in graphical mode as well as the text mode).
The machine has one network card, which is listed, and has the "[ ]" to select it, but it is not selected ([*]). And installation stops there waiting for user input.
ks.cfg file is correct.
This should be fixed in version 12.28 of anaconda.
Pablo, thanks for the report, in the end I used another patch (commit fe1208d5de4f2532180b6fb21a2605118a297840) which I have tested to work with rawhide, but I doubt it would work with fc10.
The problem is still present. And not only that...I discovered it is present also in Fedora 11 as well.
This is a major problem, as it blocks automatic installation without any workaround possible.
I am surprised that looking at the date of the creation of the bug, end February 2009, it is even in FC11. We'll see if FC12 carries also the issue. I am wondering which Fedora version could I expect to have a fix. Otherwise it would be a shame that I would have to change distro in order to have an automatic installation.
I am willing to test any potential solution, as I already did with the two patches from comment #3
I am willing to help developing the fix.
Please I need help here!!!
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
I just wanted to know if there is any hope to have a fix for this, fc10 or fc11 or fc12 or potentially fc13?
(In reply to comment #8)
> I just wanted to know if there is any hope to have a fix for this, fc10 or fc11
> or fc12 or potentially fc13?
It should be fixed in F12.
Yes. Just tested it.
Any way to fix the installer of fc11 or fc10 by backporting some code?