dhcp: an apply that moves an IP from one reservation to another is refused as a duplicate #106

Closed
opened 2026-11-11 21:58:32 +00:00 by christianmanivong · 0 comments
Owner

Live: host A holds 192.0.2.10, host B holds 192.0.2.11. Desired: B = 192.0.2.10, A = 192.0.2.20. apply_dhcp_reservationset applies the updates in the order of desired (B first), and Kea refuses B: {'result': 'failed', 'validations': {'reservation.ip_address': 'Duplicate entry exists.'}}. Applied in the other order (A first), both go through.

Expected: the apply orders its changes so an address is released before it is taken — an update that frees an IP another change needs goes first, adds after the updates that free their IP. A true cycle (A and B swap addresses) needs a temporary step or is reported as such.

Since 4.35.1 the other changes are still written and committed; the refused one stays refused.

Live: host A holds 192.0.2.10, host B holds 192.0.2.11. Desired: B = 192.0.2.10, A = 192.0.2.20. `apply_dhcp_reservationset` applies the updates in the order of `desired` (B first), and Kea refuses B: `{'result': 'failed', 'validations': {'reservation.ip_address': 'Duplicate entry exists.'}}`. Applied in the other order (A first), both go through. Expected: the apply orders its changes so an address is released before it is taken — an update that frees an IP another change needs goes first, adds after the updates that free their IP. A true cycle (A and B swap addresses) needs a temporary step or is reported as such. Since 4.35.1 the other changes are still written and committed; the refused one stays refused.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: NAPALM/napalm-device-types#106