[et-mgmt-tools] cobbler kickstart does not pull in the http: ks file?

[Michael DeHaan]

> Apr  4 15:43:23 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
> Apr  4 15:43:23 admin dhcpd: DHCPOFFER on 192.168.62.172 to
> 00:15:17:3a:c2:78 via eth0
> Apr  4 15:43:29 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
> Apr  4 15:43:29 admin dhcpd: DHCPOFFER on 192.168.62.172 to
> 00:15:17:3a:c2:78 via eth0
> Apr  4 15:43:40 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
> Apr  4 15:43:40 admin dhcpd: DHCPOFFER on 192.168.62.172 to
> 00:15:17:3a:c2:78 via eth0
> Apr  4 15:43:50 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
> Apr  4 15:43:50 admin dhcpd: DHCPOFFER on 192.168.62.172 to
> 00:15:17:3a:c2:78 via eth0
> Apr  4 15:43:50 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
> Apr  4 15:43:50 admin dhcpd: DHCPOFFER on 192.168.62.172 to
> 00:15:17:3a:c2:78 via eth0
>
> Why is it looping?
>   


Ah, the dreaded installer DHCP problem.   This seems to indicate that 
your system failed to DHCP in time.  There are known timing issues with 
Anaconda at that stage, after it resets the network card, where pump 
doesn't have a sufficiently long timeout.

Here's a custom search engine for kickstart-list at redhat.com:

http://www.google.com/coop/cse?cx=016811804524159694721%3A1h7btspnxtu

It probably is a network configuration issue -- most likely this one:

http://www.redhat.com/archives/kickstart-list/2002-August/msg00041.html

There's also a writeup here:

http://fedoraproject.org/wiki/Anaconda/NetworkIssues

Hopefully that gets you further along.   If Anaconda can't get network 
info, it will prompt for it -- it never had a chance to request the 
kickstart in your case because it didn't have an IP at that stage.

--Michael