Hi,

we are currently in the process of setting up PXE boot while the foreman installation is being used for a larger scale deployment issues. We have made the experience that foreman does not like it when subnet smart proxy settings are changed while hosts are set up for build. Edits to those hosts cannot be submitted until the subnet edit has been undone.

The error message is usually "unable to (set|delete) TFTP boot entry: 404 Resource not found". While, IMO, the tftp smart proxy is within its bounds to report that an entry that foreman wishes to delete or change is not there, foreman should handle this situation more gracefully.

Especially, it should be possible to delete a host even if its TFTP entry cannot be deleted.

While we're having this issue mainly with the TFTP smart proxy, I think this applies to the Smart Proxy interface in its entirety. I have had host edits bomb out because a DHCP subnet was doubled in the dhcpd configuration - a situation that the DHCP server itself handles gracefully, but foreman spewing errors in this case.

Greetings
Marc