Problem:
the above line in dhcpd.leases contains the start of a mac address that is unknown in our infra
Expected outcome:
the line would contain an entryrelating the Foreman proxy being used as a dhcp server
Foreman and Proxy versions:
3.6/4.8
Foreman and Proxy plugin versions:
Other relevant info: the foreman infra had to be re-built (in order to migrate from EL7 to EL8)
A lot of machines were therefore unregistered from the old and regstered to the new, without issue.
During a reboot of a VM, we saw a few that failed to boot disk due to tftp timeout. Noticed that even though I dont recognise the supercede entry on dhcpd.leases, it was very slightly different to the mac entry we had for the problem VMs. Changing to match, fixed the issue. Would like to know why as this entry does not add up.
Both tftp conf and dhcp.conf looks good with correct IP address of the proxy
e.g
working VM:
host examplehost.com {
dynamic;
hardware ethernet examplemac;
fixed-address 10.25.1.19;
supersede server.filename = “pxelinux.0”;
supersede server.next-server = 0a:19:02:0f;
supersede host-name = “examplehost.com”;
not booting:
[VM (tftp timeout) need to wait 10 mins for main boot]
host examplehost.com {
dynamic;
hardware ethernet examplemac;
fixed-address 10.25.1.20;
supersede server.filename = “pxelinux.0”;
supersede server.next-server = 0a:19:02:0e; ← notice ‘e’ not ‘f’
supersede host-name = “examplehost.com”;
Changing the below to 0a:19:02:0f fixed the issue and tftp loads straight away. No idea why. Also removing the entry fixes it.
Any clues for this would be much apprciated!