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