what version of anaconda are
you using for this? I personally don't see a way of altering the
kickstart behaviour, except by getting down and dirty in the
kickstart.py source file of anaconda, but maybe
someone else has some ideas.
Matt
Angus Clarke wrote:
Hi
I use CGI scripts to auto-generate kickstart files depending on the target's IP address - $ENV{REMOTE_ADDR}
I do this to avoid maintaining hundreds of KS files (normally one for each target server)
My situation is slightly complex as I have dozens of target networks.
We derive network information from predefined perl hash tables, where we lookup:
- default route
- dns server
- target hostname (derived from DNS of the client's IP)
I use this to generate a line such as the following in the default KS file:
<-- snip
network --device eth0 --bootproto static --ip 192.168.1.50 --netmask 255.255.255.0 --gateway 192.168.1.1 --nameserver 192.168.1.2 --hostname angus
<-- snip
Everything works great, until one of my guys rebuilds a server on some unknown network (ie not in the lookup table)
When this occurs, anaconda is fed an incomplete kickstart file - it's default behaviour then is to prompt for input.
The trouble I have with this is that we are usually rebuilding servers in remote locations without local hands!
So, we affectively lose this server until our next site visit (lights out is not configured across all our sites)
Is there some option or means of persuading anaconda to reboot on failures, prior to any changes being committed to the system? (ie. prior to fdisk activity of Kickstart file)
Thanks in advance
Angus
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
|
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
