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: When provisioning hosts using FixedAddress the Infoblox integration does not specify the DNS View in the Infoblox record it creates, which could lead to a problem if the user is using a non-default DNS or Network view.
Version-Release number of selected component (if applicable): 6.5.0
How reproducible:
Steps to Reproduce:
1. Create a non-default network view (called "othernetview"), which also create a DNS View ("default.othernetview")
2. Create a domains for forward and reverse lookups in "othernetview" and on Satellite
3. Provision a host
Actual results:
The provision will fail with this error in
Expected results:
Additional info:
We don't seem to have a way to specify the DNS view used for the Infoblox DNS plugin, only the DHCP one. However, per Infoblox's API Doc they recommend specifying it when creating 'A' Records
Verified fix in sat 6.6 snap 12
1. Created a non-default Infoblox network view (called "othernetview"), which also created a DNS View ("default.othernetview")
2. Create a domains for forward and reverse lookups in "othernetview" and on Satellite
3. satellite-installer <otherinfobloxconfig> --foreman-proxy-plugin-dns-infoblox-dns-view default.othernetview)
4. Provision a host
The records were created in the correct DNS VIew
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:3172
Description of problem: When provisioning hosts using FixedAddress the Infoblox integration does not specify the DNS View in the Infoblox record it creates, which could lead to a problem if the user is using a non-default DNS or Network view. Version-Release number of selected component (if applicable): 6.5.0 How reproducible: Steps to Reproduce: 1. Create a non-default network view (called "othernetview"), which also create a DNS View ("default.othernetview") 2. Create a domains for forward and reverse lookups in "othernetview" and on Satellite 3. Provision a host Actual results: The provision will fail with this error in Expected results: Additional info: We don't seem to have a way to specify the DNS view used for the Infoblox DNS plugin, only the DHCP one. However, per Infoblox's API Doc they recommend specifying it when creating 'A' Records