Bug 216775 - Obtaining dynamic ks.cfg does not reconfigure network
Summary: Obtaining dynamic ks.cfg does not reconfigure network
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Chris Lumens
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-11-21 22:33 UTC by Joe Ogulin
Modified: 2008-01-18 17:18 UTC (History)
0 users

Clone Of:
Last Closed: 2008-01-18 17:18:11 UTC

Attachments (Terms of Use)
CGI script used to generate dynamic KS file (3.91 KB, application/x-perl)
2006-11-21 22:33 UTC, Joe Ogulin
no flags Details

Description Joe Ogulin 2006-11-21 22:33:07 UTC
Description of problem:
When obtaining the kickstart file from a web source, the network device is not
reconfigured to match what comes in with the kickstart file.

Yes, I know the network is configured initially using DHCP, but there is a
network command in the kickstart file that specifies a static IP address, and it
is not applied prior to attempting NFS mounts.

Version-Release number of selected component (if applicable):
Fedora Core 6 (possibly prior versions as well)

How reproducible:

Steps to Reproduce:
1. Place a CGI script on a local web server to provide the kickstart file.
(Script I use is attached.)
2. Set up an NFS server that restricts access to a limited set of IP addresses
3. Set up the DHCP server to send out addresses not in the exports list from 2.
4. Boot a cd, and enter:
linux ks=http://www.example.com/cgi-bin/ks.pl?option1=x&option2=y
Actual results:
Could not mount NFS file system because the IP address is still that assigned by
the DHCP server

Expected results:
eth0 is configured with the kickstart-specified information once the kickstart
file is obtained

Additional info:

Comment 1 Joe Ogulin 2006-11-21 22:33:07 UTC
Created attachment 141843 [details]
CGI script used to generate dynamic KS file

Comment 2 Joe Ogulin 2006-11-22 16:43:52 UTC
the boot/install line should read:
or something similar

Comment 3 Chris Lumens 2008-01-18 17:18:11 UTC
This should be fixed in F9.  Loads of network config fixes have gone in.

Note You need to log in before you can comment on or make changes to this bug.