Related changes which might be interesting to investigate: #6743 #7660 #8788

I did another test, creating a new CentOS6 host dedicated to DHCP function.

After running some foreman-installer commands to deploy only the DHCP Smart Proxy, I registered it onto my running Foreman instance (all 1.8 versions)
Here are some observations :
- The current dhcpd.conf template "hardcode" the pxeserver option to the current host the smart proxy is installed in :
In /usr/share/foreman-installer/modules/foreman_proxy/manifests/proxydhcp.pp:

    pxeserver   => $ip,

<% if has_variable?( 'pxeserver' ) &&
  has_variable?( 'pxefilename' ) &&
  @pxeserver &&
  @pxefilename -%>
# PXE Handoff.
next-server <%= @pxeserver %>;
filename "<%= @pxefilename %>";
<% end -%>

- The nextServer and filename options are not passed to Smart Proxy
Here is the POST command from foreman to Smart Proxy :

POST /dhcp/10.10.46.0 HTTP/1.1
Accept: application/json
Accept-Encoding: gzip, deflate
Content-Length: 106
Content-Type: application/x-www-form-urlencoded
User-Agent: Ruby
Host: 10.10.46.120:8080

hostname=test9centos6.virtu-bench.local&mac=00%3A50%3A56%3A9f%3A58%3Aaa&ip=10.10.46.121&network=10.10.46.0

To conclude, I'd say nobody ever tried to separate TFTP from DHCP with the foreman-installer

Setting the release to ensure triage. Thanks.

Seems to be a 1.8 regression as part of the NIC reworking in #7456.

The primary boot NIC is being created as an instance of Nic::Managed through the UI, but the nextServer/filename attributes are only implemented in Nic::Bootable (a derivative of Nic::Managed), so the NIC is getting its DHCP record created with only basic attributes.

Incidentally, the dhcp_attrs method is also in Orchestration::DHCP which confused me.. the active dhcp_attrs methods seems to be in Nic::* classes.

Applied in changeset e60f079920e6b370cfb3b2b047896fcbd4794a3c.