Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1383310

Summary: on configuring infoblox dhcp, DNS providers, installers auto configures traditional providers and configs
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: DHCP & DNSAssignee: Ivan Necas <inecas>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: NightlyCC: dmitri, maurizio.antillon
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-02 20:58:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1402685    
Attachments:
Description Flags
foreman-debug none

Description Sachin Ghai 2016-10-10 11:58:15 UTC 
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:
Comment 1 Sachin Ghai 2016-10-10 12:01:57 UTC 
Created attachment 1208815 [details]
foreman-debug
Comment 4 Dmitri Dolguikh 2017-03-17 16:28:30 UTC 
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)
Comment 5 Ivan Necas 2017-04-10 11:30:33 UTC 
Based on the comments, I'm removing blocker flag from this BZ, as it's not blocking the functionality of the infoblox integration
Comment 6 Bryan Kearney 2018-08-02 20:58:14 UTC 
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.