I checked the /srv/tftp/boot/ directory: The file was there and had a size of about 30MB. I deleted the file, so it would be regenerated, when I click on “Build PXE Default” in Hosts > Provisioning Templates. But it did not get regenerated. Now, when I boot the new host I get: PXE-E32: TFTP Timeout.
Expected outcome:
The machine should boot into the OS installer.
Other relevant data: This (141.3 KB) is the output of foreman-installer --full-help This (520 Bytes) is /var/log/foreman-proxy/proxy.log (I emptied it before trying the delete, so isolate the relevant logs)
Thank you for the quick reply!
There is no firewall in my lab network. Foreman (192.168.0.240/24) is in the same subnet as my host (192.168.0.9/24). The internet gateway (router) is 192.168.0.1. So, there is no NAT. But maybe I messed the configuration anyway.
This was about an hour ago. Seems that there is some cron job or similar, which did that (I was afk the last hour). Now there are two more files in /srv/tftp/boot/:
To be honest, I am kind of surprised regarding the development of this topic. I had a similar experience before (Tasks is no longer working after update - #8 by kiigass). On one hand it is nice, that foreman is kind of “self-repairing” on the other hand I would have liked to know what the issue is and how to solve it, if it comes back.
This is the whole /var/log/foreman-proxy/proxy.log (70.5 KB)
The update of ruby-smart-proxy-remote-execution-ssh to version 0.3.0 fixed the issue with the creation of hosts and now the tftp boot is also working again. I dont really know if it was the update or the delayed download. I will mark your answer as solution. I really appreciate all your help, thank you!