Plugins » Discovery

(originally from foreman-users thread https://groups.google.com/d/msg/foreman-users/v_Tcs40XE3o/M6dAFjxlAwAJ)

Seems like disjoint dhcp ranges, as desrbribed per the docs, do not work as expected with discovery.

Setup:
1 subnet, with a dhcp range set to 192.168.1.00->192.168.1.200, and the subnet defined in foreman with 192.168.1.5->192.168.1.99 for IP selection.

Expected behavior:
Boot host to discover, host leases ip from dhcp server range (100->200), upon provisioning, foreman selects an ip from its defined range(5->99), and provisions the host with that ip address as if it was a normal host being provisioned (I'll note, this should happen before rendering the hostname from the hostname template, in the case that the hostname is based on the "new" IP address).

Actual behavior:
Boot host to discover, host leases ip from dhcp server range (100->200), upon provisioning, host is transformed directly into a managed host, never getting a new IP address assigned to it (and subsequently the @host facts are strictly based off the discovery (pre-provisioning ) facts, instead using the same (100->200) ip address.

Suggestion to fix is to have a discovery-level settings to toggle this behavior on/off