Red Hat Bugzilla – Bug 5589
6.1 kickstart doesn't look at BOOTP/DHCP next-server
Last modified: 2008-05-01 11:37:52 EDT
I have been successfully using kickstart with 5.2 and 6.0. On my BOOTP/DHCP server, I specify next-server and a kickstart filename on that server. Note that next-server is different from the BOOTP/DHCP server. In 6.1, the installer doesn't seem to pay attention to next-server, but instead tries to NFS mount the kickstart config file from the BOOTP/DHCP server. Of course this fails. Is this intentional? Is there a workaround? As it stands, it looks like I'll have to put the kickstart config on the floppy, and I'd rather not do this if I can help it.
It appears to me the change to pump caused the problem. It appears that pump ignores the next-server specification. Ugh.
It appears to me the change to pump caused the problem. It appears that pump ignores the next-server specification. Ugh. ------- Additional Comments From 10/18/99 10:57 ------- I see this on my end as well. Very frustrating.
This issue has been forwarded to a developer for further action.
*** Bug 6202 has been marked as a duplicate of this bug. *** When attempting a kickstart/DHCP/NFS install, the installer attempts to mount the DHCP server instead of the machine defined by the next-server in the dhcpd.conf: The following dhcpd.conf stanza worked w/ RH6.0, but now fails with the message "failed to mount 128.165.207.25:/root/kickstart" on the Alt+F3 console: group { filename "/root/kickstart/wyrd.node"; next-server 128.165.207.235; host forte2 { hardware ethernet 00:a0:cc:56:1c:4a; fixed-address 128.165.207.226; } } 128.165.207.25 is the IP address of the dhcpd server. ------- Additional Comments From 10/31/99 22:11 ------- GROSS HACK WARNING: Adding the non-obvious option dhcp-server-identifier 130.237.48.112; to your ISC dhcpd.conf will enable you to kickstart (at least it seams to) Love <lha@stacken.kth.se>
Just discovered this problem myself. I'll be trying to NFS mount the directory that contains all of the config files back to the DHCP server. Ugly - with out a doubt - but if I keep the paths the same it won't break when RH gets the next-server call functioning at some point.
Well that was a dumb idea - can't share and nfs mounted file system. Back to the drawing board again.
Just noticed that this is fixed in the Rawhide bootnet.img.
This is fixed for the next release (and current rawhide)