Up-front confession: 2.0.11: yes, I know, old.
We have a well-established cobbler set-up for our machines (approaching 100). These are all installed over the same network from a server on that same network (say, "network-main"). So the cobbler configuration is a straightforward single network.
But we now wish to install a couple of client machines over a different network (say "network-alt") The cobbler server also has a port onto this network. So it should be possible to do this. But how?
I tried adding this new client to the cobbler server, and the network installation began. But it quickly paused, because it seems to be trying to mount the images over the original "network-main". (I was able to proceed, because it asked me to re-enter the details, so I was able to give it the server's address on "network-alt".)
But I'd like a cleaner solution. When Cobbler produces "/etc/dhcpd.conf", each host contains a "next-server" entry, which is, of course, on "network-main". So for my new client I tried using a "--server-override=..." giving the IP address of the cobbler server on "network-alt"). Firstly, it didn't like the syntax. Google suggested trying simple "--server" keyword. That looked OK and "cobbler system report" then showed "Server Override" to have the expected "network-alt" value. Looking good.
BUT... the contents of "/etc/dhcpd.conf" still show my new host to have "next-server" on the original, old "network-main". (Yes, I had remembered the "cobbler sync".)
What am I missing? (If there's a known bug about this issue in my old version 2.0.11, then fair enough, that's my problem.)
-- David Lee