Problem:
Unable to provision with InfoBlox. It doesn’t call out to InfoBlox. So DHCP/TFP Options are not being applied. Expected outcome:
Foreman and Proxy versions:
Foreman and Proxy plugin versions:
Other relevant data:
Can anybody post their dhcp_infoblox.yml files.
---
# Configuration file for 'dhcp_infoblox' dhcp provider
#
# use :server setting in dhcp.yml if you are managing a dhcp server which is not localhost
# use :subnets setting in dhcp.yml if you want to restrict subnets available to smart-proxy
#
:username: "svc-foreman"
:password: "%$%$%$%$"
#
#
# Record type to manage: can be "host" or "fixedaddress"
#
:record_type: 'host'
#
# Use pre-definded ranges in networks to find available IP's
#
:use_ranges: true
:dns_view: "default"
:network_view: "default"
---
#
# Configuration file for 'dhcp_infoblox' dhcp provider
#
# use :server setting in dhcp.yml if you are managing a dhcp server which is not localhost
# use :subnets setting in dhcp.yml if you want to restrict subnets available to smart-proxy
#
:username: "infofloxuser"
:password: "censored"
#
# Record type to manage: can be "host" or "fixed_address"
#
:record_type: 'host'
#
# Use pre-definded ranges in networks to find available IP's
#
:use_ranges: false
I think the use_ranges option has been removed in the past, though, and the behaviour is now to always use defined ranges from Foreman (at least I could not find any references in the code or the docs). So your settings look fine to me.
Just some basic questions to be sure:
You have followed the install and config instructions from the plugin’s docs?
Can your Foreman server reach the infoblox API via https? Like curl -k https://infoblox.example.com/
In Foreman smartproxy menu (under infrastructure), does your smartproxy show the DHCP feature?
On the subnet you subnet you want to deploy to, have you set the DHCP smartproxy correctly (Infrastructure -> Subnets -> Select the subnet in question)? You will need at least these settings: IPAM set to DHCP on the subet tab, DHCP Proxy set to your smartproxy on the Proxy tab.
If nothing of the above solves your problem, can you please provide /var/log/foreman/production.log and /var/log/foreman-proxy/proxy.log of the timeframes in question when the host gets created?
Do you know if there is a way to setup a delay from when the dhcp entry is created to when the power on is sent. It looks like my machines are booting before the DHCP entry is set.
this is something that multiple users reported to us, there is a PR and you can apply it today, however the conversation is not over yet. Might get implemented differently, but I like this approach more: