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.
Bug 1752569 - [RHEL-7] Change dhcp_release to use default address when no IP subnet matches
Summary: [RHEL-7] Change dhcp_release to use default address when no IP subnet matches
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dnsmasq
Version: 7.8
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Petr Menšík
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On: 1694094
Blocks: 1757351
TreeView+ depends on / blocked
 
Reported: 2019-09-16 16:27 UTC by Andreas Karis
Modified: 2023-03-24 15:27 UTC (History)
27 users (show)

Fixed In Version: dnsmasq-2.76-11.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1694094
: 1757351 (view as bug list)
Environment:
Last Closed: 2020-09-29 19:31:26 UTC
Target Upstream Version:
Embargoed:
pdancak: needinfo+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1749092 0 urgent CLOSED [RHEL-8] Change dhcp_release to use default address when no IP subnet matches 2023-02-12 23:11:35 UTC
Red Hat Issue Tracker RHELPLAN-53487 0 None None None 2022-05-01 12:52:48 UTC
Red Hat Product Errata RHSA-2020:3878 0 None None None 2020-09-29 19:33:45 UTC

Internal Links: 1749092

Description Andreas Karis 2019-09-16 16:27:21 UTC 
Please backport http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=d9f882bea2806799bf3d1f73937f5e72d0bfc650 into RHEL dnsmasq
Comment 9 Brian Haley 2019-09-26 14:45:09 UTC 
Hi Petr,

I did look at the possibility of using D-BUS, but it was going to consume a lot more resources (one additional d-bus daemon per namespace), and make the configuration of DHCP in Openstack much more complicated.

http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2019q2/013041.html

Since we are moving away from using dnsmasq in later versions of RH Openstack I didn't feel the investment was worth it.  Unless there is a simpler way to use it?
Comment 10 Petr Menšík 2019-09-28 19:47:54 UTC 
I think it should be possible to use shared d-bus for more namespaces and use namespace in dnsmasq service name. But that might not be simpler setup in such case. Ok, if dnsmasq is going to be replaced, it might be a bit simpler.

Found example to do it on stackexchange [1]. It would need just one proxy service for all namespaces. But shared bus might be vulnerable to misconfigurations.

1. https://unix.stackexchange.com/questions/184964/connect-with-d-bus-in-a-network-namespace
Comment 13 Petr Menšík 2019-09-30 11:23:32 UTC 
(In reply to Brian Haley from comment #9)
> Since we are moving away from using dnsmasq in later versions of RH
> Openstack I didn't feel the investment was worth it.  Unless there is a
> simpler way to use it?

What services will provide DHCP and DNS in later versions of RH Openstack?
Comment 19 Petr Menšík 2019-10-01 12:43:05 UTC 
It seems to me original patch to utility is missing correction of failed send. It make send work if there is at least one IPv4 address on the interface. If there is none, it would still fail. I think in this case, the tool must report error and return non-zero exit code. There is no such change even on upstream. I would request adding it.
Comment 31 Brian Haley 2020-02-24 16:01:39 UTC 
Just asking on behalf of customer if this will be verified soon?  Thanks.
Comment 32 Petr Menšík 2020-03-10 10:39:38 UTC 
(In reply to Brian Haley from comment #31)
> Just asking on behalf of customer if this will be verified soon?  Thanks.

This bug was fixes in 7.7.z, bug #1757351. Customers should have already this fix available. This bug is still open to ensure new Y-stream contains it as well. Any customer should have update to dnsmasq-2.76-10.el7_7.1 available long before this is closed.
Comment 39 errata-xmlrpc 2020-09-29 19:31:26 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 (Low: dnsmasq 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-2020:3878
Note You need to log in before you can comment on or make changes to this bug.