Thought this was better suited for the mailing list , but hanging out on
IRC as well (AbyssOne).
I am having some issues getting foreman to play using PXE.
The environment uses puppet 3.0 , and I use nightly foreman and
foreman-proxy all on Debian 6.0 foreman runs virtualised puppet on a
physical box only difference is the kernel version due to hardware support
on the Dell servers.
I have a Puppet server in net a, a foreman server in net b (behind a
firewall NAT's etc. work)
I have in net B (this is a lab net virtualised) TFTP server running on my
foreman server and a DHCP which I manually manage the leases on for testing
purposes. This works as the systems both physical and virtual try to net
boot.
But this is where the issues start , I am not well versed enough in PXE to
see what I am missing and something is missing. For test purposes I am
using the templates for provisioning as supplied with foreman. I have
associated the pressed templates with my debian 6 OS so so far that should
be good , that would be the pressed pxe , provisioning and finish
templates. I have not associated these with environments as it doesn't fit
my end needs as things like domains etc are host based as I am wanting to
use puppet/foreman to manage 3 data centers where IP , domain names etc all
vary but the packages etc should be the same. In essence all hosts are the
same except for IP and domain names.
Anyways back on track, when I click the "Build PXE Default" I get a file
generated but this default file looks like the "PXE Default File" and this
file doesnt work with the error "could not find kernel image: menu". So
after some debugging and manual file installation I got it to work , but I
thought this part should be automated. SO nwo I think I am missing
something I am just not sure where.
By the way I have associated the "preseed default" and so on with a
hostgroup and then my default changes but it will still generate the same
error if I do not manually edit the file.
First line read : " DEFAULT menu" this doesn't work if I change this to
reflect the LABEL of the lines added via the hostgroup it will boot and
fetch a boot image.
I think my problem lays somewhere in the initial setup of the templates vs
hostgroups vs hosts vs OS, but I am not sure and I am not seeing it at this
point. I get down stream errors with the preseed templates but I think this
is related to the initial setup.
Thanks for any help.
Oh the log files , I have turned on debugging , and the foreman-proxy log
file is surprisingly empty occasional :
I, [2013-01-03T12:24:02.764746 #11489] INFO – : TFTP:
/srv/tftp/pxelinux.cfg/default entry created successfully
D, [2013-01-03T12:24:02.785457 #11489] DEBUG – : Starting task (total: 0):
wget --timeout=10 --tries=3 --no-check-certificate -nv -c
http://ftp.de.debian.org/debian/dists/squeeze/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux
-O "/srv/tftp/boot/Debian-6.0-x86_64-linux"
D, [2013-01-03T12:24:02.794239 #11489] DEBUG – : Starting task (total: 0):
wget --timeout=10 --tries=3 --no-check-certificate -nv -c
http://ftp.de.debian.org/debian/dists/squeeze/main/installer-amd64/current/images/netboot/debian-installer/amd64/initrd.gz
-O "/srv/tftp/boot/Debian-6.0-x86_64-initrd.gz"
by the way it should fetch several different boot images as I have up to 9
different CPU types and OS version combinations.Unless I understand this
fetch wrong , but it only does this if I add the pressed PXE default to a
hostgroup not in any other way.