Project

General

Profile

Actions

Bug #19258

closed

Unused IP lookup on MS DHCP 2016 raises "One or more of the parameters were invalid" error

Added by Jeff Sparrow about 7 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I was attempting to use the new dhcp api proxy in 1.14, for use in msft DHCP on server 2016. Clarification, the proxy server is on 2016. The DHCP server is 2012r2.
It seems that no matter what the subnet ranges are set to, nor if the host has leases or reservations, foreman-proxy fails to find a good IP. It doesnt even look like its tries. We attempted different settings (opening up the ranges on the scope and subnet in foreman), seeing if it matters if it has a lease or reservation or not. Nothing seemed to work for getting an unused_ip. Importing subnets does work however.

Numerous logs here. This was discussed in detail with witlessb in IRC.

https://gist.github.com/tek0011/cfc9595e9e93c45d96db29438f8fbe19 - this was after deleting the lease, then requesting a new IP (with ranges defined in the foreman subnet)
https://gist.github.com/tek0011/21922f6493525de5ecbc9eb5da4ff338 - this is what each unused_ip request looks like

I did some packet capture as well. It looks like the unused_ip requests do get to the dhcp server, and the dhcp server responds. But there are only 2 packets, unlike regular dhcp requests where there would usually be 4-8 packets (bind, auth, etc).

After moving back to 1.13 everything worked again.

Actions

Also available in: Atom PDF