On Thu, Apr 4, 2013 at 3:17 AM, <[email protected]> wrote: > Hi, > > I've just started to use Cobbler 2.3 to deploy servers. Everything works > perfectly except two things. > > [root@server ~]# cobbler status > ip |target |start |state > 10.0.0.1 |system:devxxx |Mon Dec 17 10:20:59 2012|unknown/stalled > 10.0.0.2 |system:srvyyyy|Wed Mar 13 08:52:45 2013|unknown/stalled > 10.0.0.3 |system:srvzzzz |Wed Mar 27 10:41:13 2013|unknown/stalled > 10.0.0.4 |system:srvbbbb |Thu Apr 4 09:47:47 2013|installing (10m > 8s) > 10.0.0.5 |system:srvppppp1|Tue Apr 2 12:33:04 2013|unknown/stalled > > All servers states are stalled even when all installations ended > perfectly. No mail is sent at the end of each installation. I suppose both > problems are linked. > > How does Cobbler detect when an installation ends ? Is it linked to DHCP > configuration ? In my case i use an external DHCP not managed by Cobbler > and PXE settings are changed manually. >
You must include the "kickstart_done" snippet at the end of your %post (typically it is the last line). Please see the included sample_end.ks kickstart file fo an example of its usage.
_______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
