Hi Chris,
in the dhcpd.conf file we have
filename "/export/n_os/ks/";
next-server A.B.C.D;
where A.B.C.D is the NFS host.
I'm happy to file a bugzilla report if you don't think it is a
misconfiguration on my part.
thanks
iain
--
Iain Morrison
IT Manager
MRC Epidemiology Unit
Institute of Metabolic Science
Box 285
Addenbrooke's Hospital
Hills Road
Cambridge
CB2 0QQ
Tel 01223 769200
-----Original Message-----
From: kickstart-list-bounces@xxxxxxxxxx
[mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Chris Lumens
Sent: 15 August 2011 15:33
To: kickstart-list@xxxxxxxxxx
Subject: Re: ks file not found via dhcp
> 09:24:38,293 DEBUG : activating device eth2
> 09:24:45,305 INFO : wait_for_iface_activation (2274): device eth2
> activated
> 09:24:45,317 ERROR : no bootserver was found
That's the problem right there. This is printed out in the
getFileFromNfs function, specifically in the path of looking for the
implicit kickstart file location. It means the following is failing:
server_name = nm_dhcp4_config_get_one_option(dhcp,
"server_name");
if (!server_name) {
logMessage(ERROR, "no bootserver was found");
g_object_unref(client);
return 1;
}
I wonder if that DHCP option even exists, or if this is a problem with
the NM
bindings, or what. Could you file a bug about this?
- Chris
_______________________________________________
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
