Hide Forgot
Description of problem: I was trying to configure infoblox dns, dhcp providers via foreman-installer and I used following options: ~]# foreman-installer --foreman-proxy-dhcp=true --foreman-proxy-dhcp-provider=infoblox --enable-foreman-proxy-plugin-dhcp-infoblox --foreman-proxy-dhcp-server=192.168.1.2 --foreman-proxy-plugin-dhcp-infoblox-username=admin --foreman-proxy-plugin-dhcp-infoblox-password=infoblox --foreman-proxy-dhcp-interface=virbr_infoblox --foreman-proxy-dhcp-gateway=192.168.1.1 --foreman-proxy-dns-reverse="1.168.192.in-addr.arpa" --foreman-proxy-dns-zone $(hostname -d) --foreman-proxy-plugin-dhcp-infoblox-use-ranges=true --foreman-proxy-dns=true --foreman-proxy-dns-provider=infoblox --enable-foreman-proxy-plugin-dns-infoblox --foreman-proxy-plugin-dns-infoblox-dns-server=192.168.1.2 --foreman-proxy-plugin-dns-infoblox-username=admin --foreman-proxy-plugin-dns-infoblox-password=infoblox --foreman-proxy-dns-interface=virbr_infoblox Installing Done [100%] [.......................................] Success! Installer was successfully completed. However, when I looked at /etc/dhcp/dhcpd.conf, it was configured with: --- # idmqe.lab.eng.bos.redhat.com subnet 192.168.1.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option routers 192.168.1.1; } --- Also, dns zones files auto configured with specified subnet 192.168.1.1 Version-Release number of selected component (if applicable): rubygem-smart_proxy_dhcp_infoblox-0.0.5-1.fm1_14.el7.noarch rubygem-smart_proxy_dns_infoblox-0.0.4-1.fm1_14.el7.noarch rubygem-infoblox-1.0.0-1.el7.noarch How reproducible: Steps to Reproduce: 1. configure infoblox as per above parameters 2. 3. Actual results: Expected results: /etc/dhcp/dhcpd.conf and bind dns zones files shouldn't be updated with infoblox Additional info:
Created attachment 1208815 [details] foreman-debug
Content of /etc/dhcp/dhcpd.conf (dhcpd configuration file) and dhcp_isc.yaml (smart-proxy dhcpd provider configuration file) is irrelevant and has no effect on smart-proxy as long as another dhcp module provider is configured. To verify successful installation of infoblox provider: - check dhcp.yaml has "dhcp_infoblox" provider under "use_provider" setting - check dhcp.yaml has correct server address/name under "server" setting (passed from the installer) - check dhcp_infoblox.yaml has correct settings (passed from the installer)
Based on the comments, I'm removing blocker flag from this BZ, as it's not blocking the functionality of the infoblox integration
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.