Bug #27877
DHCP conflict when editing PXE loader for existing host
Pull request:
Fixed in Releases:
Found in Releases:
Description
Our orchestration code checks existing DHCP records against MAC, IP, hostname and filename. However filename must not be included when comparing DHCP records for conflicts. This change is about removing the filename from the check so it won't issue unnecessary conflict errors on updates of PXE loader.
Related issues
Associated revisions
History
#1
Updated by Lukas Zapletal 11 months ago
Updated by - Related to Bug #21120: Multiple DHCP orchestration is no longer possible with PXELoader added
#2
Updated by Lukas Zapletal 11 months ago
- Related to Bug #26525: iPXE embedded PXE loader is causing DHCP conflict added
#3
Updated by Lukas Zapletal 11 months ago
- Description updated (diff)
#4
Updated by The Foreman Bot 11 months ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7047 added
#5
Updated by Lukas Zapletal 11 months ago
- Related to Bug #27879: iPXE Embedded loader does not put token to the DHCP filename option added
#6
Updated by Lukas Zapletal 9 months ago
- Bugzilla link set to 1778827
- Triaged changed from No to Yes
#7
Updated by The Foreman Bot 5 months ago
- Fixed in Releases 2.1.0 added
#8
Updated by Lukas Zapletal 5 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset ad0707c1a527a122d9a9097aa4f16e6c926e55eb.
Fixes #27877 - no conflicts on DHCP filename change