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 1813953 - [RFE] Free IPs Suggested are often already used in Infoblox records [NEEDINFO]
Summary: [RFE] Free IPs Suggested are often already used in Infoblox records
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infoblox integration
Version: 6.6.0
Hardware: All
OS: All
unspecified
medium with 6 votes
Target Milestone: 6.14.0
Assignee: Lukas Zapletal
QA Contact: sganar
Zuzana Lena Ansorgova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-16 14:44 UTC by roarora
Modified: 2024-02-09 13:12 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
.Infoblox plugin no longer suggests IP addresses already in use Previously, when you used the Infoblox plugin as the DHCP provider, it suggested free IP addresses that were already in use. With this fix, you can configure the plugin to check the availability of IP addresses. The availability checks are enabled by default.
Clone Of:
Environment:
Last Closed: 2023-11-08 14:17:32 UTC
Target Upstream Version:
Embargoed:
bkearney: needinfo? (dsinglet)
pgozart: needinfo? (dsinglet)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 23523 0 Normal Closed Infoblox DHCP gives unreliable free IPs 2023-03-21 15:59:18 UTC
Red Hat Issue Tracker SAT-14695 0 None None None 2023-01-05 07:20:46 UTC
Red Hat Knowledge Base (Solution) 6620001 0 None None None 2022-01-04 04:28:20 UTC
Red Hat Product Errata RHSA-2023:6818 0 None None None 2023-11-08 14:17:51 UTC

Description roarora 2020-03-16 14:44:21 UTC 
Description of problem:

When provisioning using Infoblox as DHCP provider, the free IP suggested is often already taken in infoblox records.

It seems that foreman-proxy just pings a random IP and selects it as free IP.

Pinging is blocked at times or host are down. In Satellite 6.7, pinging is optional via a setting but I am not sure how it will affect this behaviour. 

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

Expected results:

foreman-proxy should check with infoblox and offer only unused IPs.
Comment 4 Lukas Zapletal 2020-03-18 10:12:30 UTC 
Hello, let me explain how Infoblox integration was implemented into Satellite.

Our DHCP Capsule has a simple API to add/delete records and to find a free IP. It simply fetches all available IP reservations and picks the first free IP from the given range, tries to ICMP/TCP ping that IP and return it if it does not respond (this behavior can be turned off in newest version of Satellite). However it does NOT perform reservation via Infoblox IPAM API. This is the limitation of the currennt design where DHCP free IP handling is done by common DHCP module and implementations are not allowed to modify this behavior.

One of our upstream users suggested to perform PTR DNS search in addition to pings to ensure the IP is free, we could implement that. We are unlikely to rewrite DHCP handling completely from scratch in order to allow tighter Infoblox integration. However External IPAM feature is already in the works, we could write a provider for Infoblox that would actually allocate IP addresses using Infoblox instead of our DHCP Capsule. That would be the cleanest solution.
Comment 6 Lukas Zapletal 2020-03-31 14:57:06 UTC 
At the moment, DHCP IPAM only avoids reservation on that DHCP server. It assumes that Satellite manages the network anyway, so all hosts from Satellite inventory are there. It does not perform a "cross-check", no.
Comment 18 George R 2022-07-11 16:33:41 UTC 
I am asking the community to look into this issue again.  This isn't working for me as well on satellite 6.10.  It's probably time for a review and refresh of the smart-proxy as Infoblox NIOS API is now at 2.12.  Thank you.
Comment 19 Brad Buckingham 2022-09-02 20:25:18 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 23 Bryan Kearney 2022-09-20 12:01:28 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/23523 has been resolved.
Comment 28 sganar 2023-06-01 12:18:55 UTC 
Verified.

Tested on Satellite 6.14.0 snap 1

Steps followed: 
1. Satellite + Infoblox Integration
2. provision a host and note the IP
3. Again provision some hosts and check if the IP suggested is not already in use 

Observation: 
Satellite and Infoblox Integration is working fine and the free IPs suggested while creating a host are not already used.
Comment 32 errata-xmlrpc 2023-11-08 14:17:32 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.14 security and bug fix update), 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-2023:6818
Note You need to log in before you can comment on or make changes to this bug.