Hi, > I am in an environment where I cannot control DHCP, so I have gone > to using Cobbler buildISO's to boot new installs.
That's a common and widespread misconception, regrettably :-( You *never* need to have direct control of a DHCP server to be able to use PXE boot with cobbler. The two DHCP servers that cobbler 2.2.3 (and later versions) work with OOTB: ISC DHCP and dnsmasq, both can act either as the authoritative DHCP for selected MAC addresses or simply just as proxies. Please check the relevant man page depending on your own preference. cobbler hides some details, but my first hand experience has indicated that I still need to know *really* well the tools that it attempts to integrate to master cobbler. You use image booting only if 0. The OS (e.g. MS Windows) is not amenable for PXE booting via cobbler (yet) 1. You need fast start-up, e.g. your environment is like AWS EC2 or a virtual server hosting provider's such as linode's. There might be some other usages at this moment I can't recall. But PXE booting is clean, and fast enough for most situations. > > Today, for no reason I can locate, the process stops on a > screen saying it cannot load the kickstart file. > The given URL is valid and contains a proper, > cobbler-generated kickstart. Do a cobbler system getks --name=... Can you see the rendered kickstar file? > > I checked firewalls, restarted apache, restarted cobblerd, > did a "cobbler sync" and still the same roadblock. These come later. Please do the above first. Always as the first step, often in conjunction with cobbler system dumpvars --name=... |less as a helpful companion. [...] HTP -- Zack _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
