Bug 1383334

Summary: Valid provider names needs to be updated in /etc/foreman-proxy/settings.d/{dns, dhcp}.yml
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: DHCP & DNSAssignee: Ivan Necas <inecas>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: NightlyCC: dmitri
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 21:00:25 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:
Bug Depends On:    
Bug Blocks: 1402685    

Description Sachin Ghai 2016-10-10 12:37:41 UTC
Description of problem:

dns.yml currently list following valid providers:

# valid providers:
#   dns_dnscmd (Microsoft Windows native implementation)
#   dns_nsupdate
#   dns_nsupdate_gss (for GSS-TSIG support)
#   dns_libvirt (dnsmasq via libvirt)

this needs to be updated with dns_infoblox 

similarly, dhcp.yml lists following valid providers:

# valid providers:
#   - dhcp_isc (ISC dhcp server)
#   - dhcp_native_ms (Microsoft native implementation)
#   - dhcp_libvirt (dnsmasq via libvirt)

this needs to be updated with dhcp_infoblox as well

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:
always

Steps to Reproduce:
1. 
2.
3.

Actual results:
 Infoblox is missing in Valid Providers under:
 /etc/foreman-proxy/settings.d/{dns, dhcp}.yml

Expected results:
Valid Providers needs to be updated with infoblox in below files:
 /etc/foreman-proxy/settings.d/{dns, dhcp}.yml

Additional info:

Comment 3 Dmitri Dolguikh 2018-02-28 22:23:50 UTC
Infoblox providers are not part of core smart-proxy, and shouldn't be listed in example configuration files.

If such examples are necessary, they should come in packages containing these providers.

Comment 4 Bryan Kearney 2018-08-02 21:00:25 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.