Kelsey,

Thanks for the offer.

I am only using cobbler to manage DHCP, as I am using PowerDNS with a MySQL backend and haven't found time to investigate cobbler/PowerDNS integration.

As for running cobbler sync, I use both the CLI cobbler sync and the sync "button" that is available via the webUI. In this case I believe I used the webUI to do the sync, after having found an error with the dhcp configure for the target subnet.

I did not however run it after adding the new system.

David

On 02/23/2010 12:21 PM, Kelsey Hightower wrote:

I would be glad to try and help you out, but I will require a bit more info.

Are you using cobbler to manage DNS and DHCP?

If so, have you run a cobbler sync after adding the new system entry to regenerate the DHCP and DNS info?

On Tue, Feb 23, 2010 at 12:36 PM, Adurotec <info@adurotec.com> wrote:

I have been using cobbler 1.6.6 for my vmware esxi 4.0 CentOS 5.4 i386 installs with no problem. I imported the i386 5.4 DVD and created a kickstart template for all of the servers I have setup.

Now I am trying to do the same thing for the 64 bit version of CentOS 5.4 within a vmware guest, the install makes it to the boot menu, but once I make a choice and proceed with the install I get prompted for the TCP/IP configuration. Once I put that information in the install proceeds unattended.

It looks like the DHCP assignment for the installer is failing, but I am not sure where to check to verify that is indeed the problem or if it is something else.

Could someone help point me in the right direction.

Thanks,
David

_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
  