RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
dhcp_release utility in dnsmasq doesn't always send a release if system is not in the same subnet as the leasee

The bug I linked, https://bugzilla.redhat.com/show_bug.cgi?id=1694094 is for Red Hat Openstack, and the issue is something I tracked-down and fixed in upstream dnsmasq yesterday:

http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=d9f882bea2806799bf3d1f73937f5e72d0bfc650

We need this change in order for dhcp_release to run successfully in certain Edge deployments where we are using a DHCP relay sending packets to a centralized DHCP server, there is more information in the original bug and the commit message in the patch.

Let me know if there are any question on the request, didn't know the best way to get the package updated so an OSP customer can consume it.  I also need to check if they need this on 7.x, which I'll open in a separate bug, assuming that backport would be possible.


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

How reproducible:
Very

Steps to Reproduce:
1. Run dhcp_release with an address not in the local subnet and watch with tcpdump that no release is sent
2.
3.

Actual results:
Should see release sent on loopback


Expected results:


Additional info:

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-2020:1715