Project

General

Profile

Actions

Refactor #19706

closed

Don't treat DHCP leases as conflicts

Added by Lukas Zapletal about 7 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Category:
DHCP
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Our previous code that should ignore leases was based on existence of hostnames, it used to work but no longer works in recent releases. In smart-proxy, we added explicit flag to indicate if a DHCP record is a reservation or a lease: theforeman/smart-proxy#532

This patch leverages this and removes the old hostname "hack" to proper test if the existing record is a lease or not. Conflict is not thrown in that case.


Related issues 2 (0 open2 closed)

Related to Smart Proxy - Feature #19666: Return record type for DHCP recortsClosedLukas Zapletal05/25/2017Actions
Related to Foreman - Bug #21120: Multiple DHCP orchestration is no longer possible with PXELoaderClosedLukas Zapletal09/27/2017Actions
Actions

Also available in: Atom PDF