After the seed file execution is complete (and beyond even preseed
_late_default) /etc/network/interfaces is being overwritten by the
finish-install process.That means that the custom /e/n/i file generated
and put in place by post_install_network_config_deb is simply wiped
out. You're
Okay, here's what I'm running into now...
I have a system that I just rebuilt as my host server. Everything built
without a hitch.
However, now, I've added a distro, two profiles, and a system.
The system definition ends up in the dhcp config file but the sync
process does NOT build the PXE
Yeah, I perhaps could've been more clear: finish-install belongs to the
debian installer - not part of cobbler. finish-install runs *after* the
preseed file is all said and done with but before the system is rebooted.
By the time preseed is done so is Cobbler's ability to have any further
Nah, it's not your fault, it's mine as I'm still confused about the
relationships of the various components of the build environment. To your
example, the finish-install stuff is under
/srv/www/cobbler/ks_mirror/$distro/... so to me it looks like it's part of
cobbler. As I mentioned, I'm not clear
if you are using the python tftp server these system definitions don't get
generated iirc.
check with: grep ^module.*tftp.* /etc/cobbler/modules.conf
On Thu, Jul 31, 2014 at 8:45 PM, Michael Tiernan mtier...@mit.edu wrote:
Okay, here's what I'm running into now...
I have a system that I
On 7/31/14 2:57 PM, Jörgen Maas wrote:
if you are using the python tftp server these system definitions don't
get generated iirc.
I'm sorry, maybe I'm dense. I'm obviously saying the wrong thing here
because the tftp server selection doesn't change this. (I've tested it too.)
When the target
Check next_server in /etc/cobbler settings, restart xinetd, add -v (or
-vv or -vvv) to /etc/xinetd.d/tftp file, what is in
/var/lib/tftp/pxelinux.cfg? Is there a file with the mac address in this
dir? Check logging in /var/log/messages... All this should give you an
idea of what is going on.
