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 1724201 - [Tracker] Infoblox update for Satellite 6.5.z
Summary: [Tracker] Infoblox update for Satellite 6.5.z
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infoblox integration
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks: 1705546 1712283 1720200
TreeView+ depends on / blocked
 
Reported: 2019-06-26 12:55 UTC by Lukas Zapletal
Modified: 2021-09-09 13:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-25 07:57:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Zapletal 2019-06-26 12:55:51 UTC
Multiple customers are reporting various problems with Infoblox integration. Workarounds are not straightforward and require code patches, this is a tracker and request for 6.5 z-stream. Multiple bugfixes will be provided in this errata.

Comment 4 Lukas Zapletal 2019-06-26 14:21:59 UTC
SUMMARY:

Problem: Infoblox cluster is slow to commit changes, VM boots and DHCP does not have the record ready.
Solution: Configurable delay so Foreman waits before VM is launched.

Problem: Proxy DNS module performs DNS lookup before record is added, but it does it via Ruby DNS stack against server set in dns_server. Infoblox clusters are often configured in a way that the member which is providing the API does not provide DNS services.
Solution: Introduce short-term workaroud of env. variable to override DNS server for lookups.
Long term solution (needs to be ready in 6.6): Redesign DNS smart proxy API to allow Infoblox module to query via REST API.

Problem: Ability to provide custom DHCP options in settings.
Solution: Added the config.

Problem: Inability to set DNS view in configuration (reported by QA)
Solution: Added the config.

Comment 5 Lukas Zapletal 2019-07-25 07:57:27 UTC
We are not doing errata for infoblox issues in 6.5, however we will be able to provide updated RPM packages for customers with 6.5 as a hotfix.


Note You need to log in before you can comment on or make changes to this bug.