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.
DescriptionJoniel Pasqualetto
2022-02-10 16:42:24 UTC
Description of problem:
The behaviour of DHCP reservations created by the Infoblox smart proxy currently does not match the behaviour of DHCP reservations created by the isc-dhcpd smart proxy: specifically, Infoblox does not seem to send the client host name in the offer (option 12, "host-name") unless the reservation contains an explicit DHCP option for that.
In other words, setting the "name" field when creating the fixedaddress is not enough for Infoblox to send the "host-name" DHCP option.
On the other hand, the isc-dhcpd smart proxy creates reservations with supersede host-name, causing the host name to be included in the response.
A solution is to add an explicit "host-name" option to all fixedaddress records, making the Infoblox smart proxy behave more like the isc-dhcpd one.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Infoblox does not send host-name (dhcp client option 12) in the dhcp offer.
Expected results:
Infoblox send host-name (dhcp client option 12) in the dhcp offer.
Additional info:
There is a PR upstream implementing the change, in a way that foreman-proxy plugin creates the reservation on infoblox and sets the option 12.
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.