May I suggest you to check the following? 0. Do you use ISC DHCP server, or the dnsmasq? Does cobbler manage it? 1. Have you used cobbler system getks --name=... to check your rendered kickstart file? Do you see the desired IP in the rendered version? 2. Have you used cobbler cobbler system dumpvars --name=... to examine all variables? 3. Have you checked your installation log and see what the actions have been taken for your installation?
Typically, after the above four steps, and assuming for 0, you have *really* acquainted yourself with the respective man page of the two DHCP servers, you should be able to make a static IP assignment for Red Hat alike systems without a hitch. Per my first hand experience, with Red Hat alike systems, static IP address assignment is quite doable. For Debian/Ubuntu, the presence of a DHCP server *NOT* under your control does take some doing, but still doable. Worst comes to the worst, you have the cobbler built-in configuration management features come to your rescue. I have found that the 'Template Files' attribute for both profile and system objects, together with the bundled download snippet, as the last, but very reliable, resort. In fact, I use this mechanism for assigning static IP address to Debian/Ubuntu nodes (both physical and virtual) even when I don't have control (or prefer not to control) the existing DHCP server . Works like a charm. Regards, -- Zack > I am having the same problem. > Cobbler 2.2.3. > > I have checked that the MAC address and interface name > matches the interface that has a static IP assigned in cobbler, > but Anaconda still prompts for an IP. I have set management=true > on the _other_ interface as well, so I would > expect cobbler to be using that interface to install. > _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
