Perfect, got it fixed, I have to define a Subnet in foreman.
Same problem here using Foreman 1.8.3 I don't find out in logs or anywhere
else what is the problem, The subnet exists and so forth,
···
On Saturday, March 2, 2013 at 12:11:20 AM UTC+1, svc.r...@gmail.com wrote: > > Perfect, got it fixed, I have to define a Subnet in foreman. > > On Thursday, February 21, 2013 6:52:03 PM UTC-5, svc.r...@gmail.com wrote: >> >> I am new to Foreman, >> >> I am trying to provision a VM on an ESX host, foreman does not update >> /var/lib/tftpboot/pxelinux.cfg >> >> with the new host information when I click on build host. I have the >> right permission set on this folder. >> >> [root@poc01 tftpboot]# ls -ld /var/lib/tftpboot/pxelinux.cfg >> drwxr-xr-x 2 foreman-proxy root 4096 Feb 21 18:30 >> /var/lib/tftpboot/pxelinux.cfg >> [root@poc01 tftpboot]# >> >> >> [root@poc01 tftpboot]# ls -l /var/lib/tftpboot/pxelinux.cfg >> total 4 >> -rw-r--r-- 1 foreman-proxy foreman-proxy 161 Feb 21 18:30 default >> [root@poc01 tftpboot]# >> >> is there anything I need to look at, I was expecting to see a pxe config >> file for the host with the host Mac >> address as the filename. >> >> Thanks. >> >"hammer subnet info --name=…" output might be useful so we can see.
Check that you have a TFTP Proxy associated to the subnet and that the
subnet is specified on the provisioning interface of your host.
Click "Cancel Build" and then "Build" to regenerate the files, or create
a new host.
···
On 24/08/15 13:52, Teoman Onay wrote: > Same problem here using Foreman 1.8.3 I don't find out in logs or > anywhere else what is the problem, The subnet exists and so forth,,,–
Dominic Cleal
Red Hat Engineering