Red Hat Bugzilla – Bug 679825
Static network configuration in kickstart doesn't work.
Last modified: 2011-04-05 17:39:48 EDT
Created attachment 480499 [details]
patch with fix
This is on f15 Alpha TC2
Install with kickstart from cd or hdd (so that network doesn't go up to fetch it). Instead of static config from kickstart, default dhcp is used.
Attaching patch with fix.
Proposing as f15 blocker.
Adding to F15Beta per the beta release criteria :
"8. The installer must be able to use all kickstart delivery methods"
Fixed in master, anaconda-16.1-1.
(In reply to comment #3)
> Fixed in master, anaconda-16.1-1.
16.2-1 it is.
Should be fixed in anaconda-15.23-1.
(In reply to comment #2)
> Adding to F15Beta per the beta release criteria :
> "8. The installer must be able to use all kickstart delivery methods"
>  https://fedoraproject.org/wiki/Fedora_15_Beta_Release_Criteria
That specific criteria was intended to capture ks= delivery methods. I don't think we have specific criteria that cover specific kickstart commands or options (outside of any intersection those commands/options have with existing criteria). I still have it on my plate to draft some kickstart-related release criteria.
This bug definitely qualifies as a Nice to have, and since we aren't in a freeze, you are more than welcome to commit a fix for this.
anaconda-15.26-1.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-15.26-1.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-15.26-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.