Bug #21120
closed
Multiple DHCP orchestration is no longer possible with PXELoader
Description
Hey,
since upgrading from foreman 14.x to 15.4 we have issues when modifying dhcp entries.
whenever we chage the bootloader from Grub2 UEFI to PXELinux BIOS, or vice versa, the foreman smart proxy start creating duplicate dhcp entries for this host.
how to repoduce:
1. create host with PXELinux BIOS bootloader
2. modify host to to use Grub2 UEFI
2. press submit (you will get a modal saying there already is a dhcp enty, and if you like to overwrite it)
3. acknowledge the modal and press the "overwrite" botton
4. now the "submit" button of the host is named "overwrite" -> press it
5. you will get a error message, complaining about a HTTP 409 from the dhcp smart proxy
if you check the leases file of the dhcp server, you will now have at least 2 entries for the same host. i have already see up to 33 entries for the same host within a file.
it also seems that the deleting a host will not always remove a entry from the dhcp leases file, but i have to admit that i am not 100% sure if the host will directly disappear from the leases file after it has been deleted.
to "fix" the issue, you have to:
- delete the host
- stop dhcpd
- remove broken entries from leases file
- start dhcpd
- recreate the host
here is a example from broken dhcp entries for the same host:
host samplehost.example.com {
dynamic;
deleted;
}
host samplehost.example.com {
dynamic;
hardware ethernet 00:50:56:91:a2:84;
fixed-address 172.21.55.57;
supersede server.filename = "pxelinux.0";
supersede server.next-server = ac:15:3a:05;
supersede host-name = "samplehost.example.com";
}
host samplehost.example.com {
dynamic;
deleted;
}
host samplehost.example.com {
dynamic;
hardware ethernet 00:50:56:91:9b:fb;
fixed-address 172.21.55.57;
supersede server.filename = "pxelinux.0";
supersede server.next-server = ac:15:3a:05;
supersede host-name = "samplehost.example.com";
}
host samplehost.example.com {
dynamic;
deleted;
}
host samplehost.example.com {
dynamic;
hardware ethernet 00:50:56:91:d5:f7;
fixed-address 172.21.55.57;
supersede server.filename = "pxelinux.0";
supersede server.next-server = ac:15:3a:05;
supersede host-name = "samplehost.example.com";
}
host samplehost.example.com {
dynamic;
deleted;
}
host samplehost.example.com {
dynamic;
hardware ethernet 00:50:56:91:ae:e9;
fixed-address 172.21.55.57;
supersede server.filename = "pxelinux.0";
supersede server.next-server = ac:15:3a:05;
supersede host-name = "samplehost.example.com";
}
Updated by Lukas Zapletal over 7 years ago
- Related to Refactor #19706: Don't treat DHCP leases as conflicts added
Updated by
Updated by Lukas Zapletal over 7 years ago
- Subject changed from DHCP duplicate entries in Foreman 1.15.4 to Updating PXE loader causes DHCP conflicts
- Status changed from Need more information to New
Updated by Lukas Zapletal over 7 years ago
- Related to Bug #21482: Unable to change host's PXE loader added
Updated by
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Assignee set to Lukas Zapletal
- Pull request https://github.com/theforeman/foreman/pull/5079 added
Updated by Lukas Zapletal over 7 years ago
- Subject changed from Updating PXE loader causes DHCP conflicts to Multiple DHCP orchestration is no longer possible with PXELoader
Updated by The Foreman Bot over 7 years ago
- Pull request https://github.com/theforeman/foreman/pull/5085 added
Updated by Lukas Zapletal over 7 years ago
- Related to Bug #21975: DHCP filename option is ignored added
Updated by Lukas Zapletal over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Updated by Daniel Lobato Garcia over 7 years ago
- Translation missing: en.field_release set to 332
Updated by
Updated by Lukas Zapletal over 6 years ago
- Related to Bug #26104: Multiple NIC orchestrations are not orchestrated added
Updated by Lukas Zapletal over 5 years ago
- Related to Bug #27877: DHCP conflict when editing PXE loader for existing host added