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 1715999 - Use Infoblox API for DNS conflict check and not system resolver
Summary: Use Infoblox API for DNS conflict check and not system resolver
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infoblox integration
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: Lukas Zapletal
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-31 23:00 UTC by Alexey Masolov
Modified: 2023-03-24 14:52 UTC (History)
4 users (show)

Fixed In Version: tfm-rubygem-smart_proxy_dns_infoblox-1.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:58:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27174 0 Normal Closed Implement REST API-based DNS conflict check 2021-01-29 13:39:31 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 12:58:50 UTC

Description Alexey Masolov 2019-05-31 23:00:49 UTC 
Description of problem:

Satellite 6.5 is configured with InfoBlox integration. The Infoblox architecture is complex (HA, multiple nodes) so requests take some time to come back. It's a common situation to run into timeouts while provisioning clients.

Version-Release number of selected component (if applicable):
Satellite 6.5

How reproducible:
100%

Actual results:
===
Create IPv4 DNS record for client.example.com task failed with the following error: ERF12-2357 [ProxyAPI::ProxyException]: Unable to set DNS entry ([RestClient::Exceptions::ReadTimeout]: Timed out reading data from server) for Capsule https://satellite.example.com:9090/dns
===


Expected results:
The client created successfully

Additional info:
Lzap advised on increasing timeout by changing the code as a workaround
Comment 4 Lukas Zapletal 2019-06-12 07:44:43 UTC 
For the record, this did not help to the customer and it looks like timeout is caused by something else. Currently it looks like a stale HTTP connection.
Comment 9 Lukas Zapletal 2019-06-26 12:28:36 UTC 
I am turning this BZ into the correct problem - it was not caused by read timeout from Infoblox API but rather by system DNS resolver unable to resolve name which is done by common DNS smart proxy code. We are going to refactor the DNS API in a way that Infoblox module can override the DNS check and provide API call instead real DNS UDP comm.
Comment 10 Lukas Zapletal 2019-06-26 13:00:45 UTC 
For the record, short term solution until we fix this bug is tracked at:

https://bugzilla.redhat.com/show_bug.cgi?id=1720200

I am proposing this short term solution (environmental variable defining a DNS server to use) into 6.5 update.
Comment 11 Lukas Zapletal 2019-11-22 14:42:07 UTC 
Fixed in 6.7.
Comment 12 Radovan Drazny 2020-10-01 10:42:46 UTC 
Tested with Sat 6.8 Snap 17 with a Infoblox instance enabled as a DNS provider. Check for an existing DNS record during a new new host creation was performed successfully, even with DNS resolving on Infoblox disabled. Creation of a new host produces following records in /var/log/foreman-proxy/proxy.log:

2020-10-01T04:55:22 d1d4fd9b [I] Started GET /dhcp/10.1.4.96/unused_ip mac=b6:6f:48:53:44:f7&from=10.1.4.101&to=10.1.4.105
2020-10-01T04:55:22 d1d4fd9b [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/network?_max_results=1&_return_fields=comment%2Cextattrs%2Cnetwork%2Cnetwork_view%2Cnetwork_container&network=10.1.4.96&network_view=default
2020-10-01T04:55:22 d1d4fd9b [I] Status 200
2020-10-01T04:55:22 d1d4fd9b [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/fixedaddress?_max_results=1&_return_fields=extattrs%2Cipv4addr%2Cmac%2Cname%2Cnetwork%2Cnetwork_view%2Coptions%2Cmatch_client%2Cbootfile%2Cuse_bootfile%2Cnextserver%2Cuse_nextserver%2Ccomment&mac=b6%3A6f%3A48%3A53%3A44%3Af7&network_view=default
2020-10-01T04:55:23 d1d4fd9b [I] Status 200
2020-10-01T04:55:23 d1d4fd9b [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/network?_max_results=1&_return_fields=comment%2Cextattrs%2Cnetwork%2Cnetwork_view%2Cnetwork_container&network=10.1.4.96&network_view=default
2020-10-01T04:55:23 ad9c563e [I] Started GET /dhcp/10.1.4.96/unused_ip from=10.1.4.101&to=10.1.4.105
2020-10-01T04:55:23 ad9c563e [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/network?_max_results=1&_return_fields=comment%2Cextattrs%2Cnetwork%2Cnetwork_view%2Cnetwork_container&network=10.1.4.96&network_view=default
2020-10-01T04:55:23 d1d4fd9b [I] Status 200
2020-10-01T04:55:23 d1d4fd9b [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/fixedaddress?_max_results=2147483646&_return_fields=extattrs%2Cipv4addr%2Cmac%2Cname%2Cnetwork%2Cnetwork_view%2Coptions%2Cmatch_client%2Cbootfile%2Cuse_bootfile%2Cnextserver%2Cuse_nextserver%2Ccomment&network=10.1.4.96%2F28&network_view=default
2020-10-01T04:55:23 ad9c563e [I] Status 200
2020-10-01T04:55:23 ad9c563e [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/network?_max_results=1&_return_fields=comment%2Cextattrs%2Cnetwork%2Cnetwork_view%2Cnetwork_container&network=10.1.4.96&network_view=default
2020-10-01T04:55:23 d1d4fd9b [I] Status 200
2020-10-01T04:55:23 d1d4fd9b [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/network?_max_results=1&_return_fields=comment%2Cextattrs%2Cnetwork%2Cnetwork_view%2Cnetwork_container&network=10.1.4.96&network_view=default
2020-10-01T04:55:23 ad9c563e [I] Status 200
2020-10-01T04:55:23 ad9c563e [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/fixedaddress?_max_results=2147483646&_return_fields=extattrs%2Cipv4addr%2Cmac%2Cname%2Cnetwork%2Cnetwork_view%2Coptions%2Cmatch_client%2Cbootfile%2Cuse_bootfile%2Cnextserver%2Cuse_nextserver%2Ccomment&network=10.1.4.96%2F28&network_view=default
2020-10-01T04:55:23 d1d4fd9b [I] Status 200
2020-10-01T04:55:23 d1d4fd9b [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/lease?_return_fields=address%2Cbinding_state%2Cclient_hostname%2Cends%2Chardware%2Cnetwork%2Cnetwork_view%2Cprotocol%2Cstarts&address~=10%5C.1%5C.4%5C.%280%3F9%5B789%5D%7C10%5B0123456789%5D%7C110%29
2020-10-01T04:55:23 ad9c563e [I] Status 200
2020-10-01T04:55:23 ad9c563e [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/network?_max_results=1&_return_fields=comment%2Cextattrs%2Cnetwork%2Cnetwork_view%2Cnetwork_container&network=10.1.4.96&network_view=default
2020-10-01T04:55:23 d1d4fd9b [I] Status 200
2020-10-01T04:55:23 d1d4fd9b [W] No free IPs in range 10.1.4.101..10.1.4.105.
2020-10-01T04:55:23 d1d4fd9b [I] Finished GET /dhcp/10.1.4.96/unused_ip with 200 (1336.4 ms)
2020-10-01T04:55:24 ad9c563e [I] Status 200
2020-10-01T04:55:24 ad9c563e [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/lease?_return_fields=address%2Cbinding_state%2Cclient_hostname%2Cends%2Chardware%2Cnetwork%2Cnetwork_view%2Cprotocol%2Cstarts&address~=10%5C.1%5C.4%5C.%280%3F9%5B789%5D%7C10%5B0123456789%5D%7C110%29
2020-10-01T04:55:24 ad9c563e [I] Status 200
2020-10-01T04:55:24 ad9c563e [W] No free IPs in range 10.1.4.101..10.1.4.105.
2020-10-01T04:55:24 ad9c563e [I] Finished GET /dhcp/10.1.4.96/unused_ip with 200 (1073.74 ms)
2020-10-01T04:55:29 2f3cd8f7 [I] Started GET /dhcp/10.1.4.96/unused_ip from=10.1.4.101&to=10.1.4.105
2020-10-01T04:55:29 2f3cd8f7 [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/network?_max_results=1&_return_fields=comment%2Cextattrs%2Cnetwork%2Cnetwork_view%2Cnetwork_container&network=10.1.4.96&network_view=default
2020-10-01T04:55:29 2f3cd8f7 [I] Status 200
2020-10-01T04:55:29 2f3cd8f7 [I] GET https://env-infoblox-01.infra.sat.rdu2.redhat.com/wapi/v2.0/network?_max_results=1&_return_fields=comment%2Cextattrs%2Cnetwork%2Cnetwork_view%2Cnetwork_container&network=10.1.4.96&network_view=default
2020-10-01T04:55:29 2f3cd8f7 [I] Status 200
Comment 15 errata-xmlrpc 2020-10-27 12:58:35 UTC 
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 (Important: Satellite 6.8 release), 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-2020:4366
Note You need to log in before you can comment on or make changes to this bug.