Red Hat Bugzilla – Bug 5605
Kickstart, NFS, and --bootproto static
Last modified: 2008-05-01 11:37:52 EDT
If you use ks=floppy with NFS, the loader configures networking via DHCP and ignores the network config in the kickstart file. This fails horribly on my network because the addresses in the DHCP pool don't have names (I don't know why -- not my DHCP or DNS server) and the NFS server doesn't like to serve clients without host names. I'm trying to use --bootproto static so I can assign a static IP address that has a proper host name to each client machine and avoid the NFS server's objections. Check out the code near anaconda/loader/net.c:511 which reads something like this: > if (!bootProto) > bootProto = "dhcp"; > > if (!bootProto) { > if (ksGetCommand ... > : > : /* reads ks.cfg network info */ > : Yikes.
This issue has been forwarded to a developer for further action.
I have this problem as well and its *really* annoying. It is severely holding up a larger scale deployment of Linux within our division. I will be willing to test any fixes to this on a moments notice. Just send me a new bootnet.img file. --John C
I'm having a similar, yet altogether different problem. When doing a netboot with the ks=floppy, I am specifying a static IP in the ks.cfg file. The thing is that is still hits my dhcp server and tries to continue that way. Needless to say, it's not joyous in the least. Sigh...just one of the many bugs that I'm finding in kickstart. Just need to figure out the rest of them now. :)
This issue is resolved in the latest installer available in beta.