Bug 1752569

Summary: [RHEL-7] Change dhcp_release to use default address when no IP subnet matches
Product: Red Hat Enterprise Linux 7 Reporter: Andreas Karis <akaris>
Component: dnsmasqAssignee: Petr Menšík <pemensik>
Status: CLOSED ERRATA QA Contact: Petr Sklenar <psklenar>
Severity: high Docs Contact:
Priority: high    
Version: 7.8CC: agurenko, akaris, amuller, atragler, bcafarel, bfournie, bhaley, chrisw, dsneddon, harsh.kotak, hjensas, jslagle, marjones, ohochman, owalsh, pdancak, pemensik, pmosko, psklenar, pvlasin, qe-baseos-daemons, ralonsoh, scohen, shdunne, slinaber, thozza, yobshans
Target Milestone: rcKeywords: AutoVerified, TestCaseProvided, Triaged, ZStream
Target Release: ---Flags: pdancak: needinfo+
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: dnsmasq-2.76-11.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1694094
: 1757351 (view as bug list) Environment:
Last Closed: 2020-09-29 19:31:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1694094    
Bug Blocks: 1757351    

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