Bug 2120763
| Summary: | Restarting NM does not kill the dnsmasq instances when dns=none defined in NetworkManager.conf | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Wen Liang <wenliang> | ||||
| Component: | NetworkManager | Assignee: | Wen Liang <wenliang> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Matej Berezny <mberezny> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 8.8 | CC: | bgalvani, djasa, lrintel, rkhan, sfaye, sukulkar, till, vbenes | ||||
| Target Milestone: | rc | Keywords: | Bugfix, Triaged | ||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | NetworkManager-1.40.10-1.el8 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-05-16 09:04:54 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Wen Liang
2022-08-23 17:10:54 UTC
The PR was merged in upstream, and I tested it, the running dnsmasq instance which started by NM was killed during restart when dns=none defined in NetworkManager.conf. Thus, change the state into `post`. Clear reproducer - qa_ack+
[root@rhel-87-nightly NetworkManager-ci]# cat << EOF > /etc/NetworkManager/conf.d/90-dnsmasq.conf
> [main]
> dns=dnsmasq
> EOF
[root@rhel-87-nightly NetworkManager-ci]# systemctl restart NetworkManager
[root@rhel-87-nightly NetworkManager-ci]# pgrep -laf dnsmasq
1914 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/NetworkManager/dnsmasq.pid --listen-address=127.0.0.1 --cache-size=400 --clear-on-reload --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d
[root@rhel-87-nightly NetworkManager-ci]# rm /etc/NetworkManager/conf.d/90-dnsmasq.conf
rm: remove regular file '/etc/NetworkManager/conf.d/90-dnsmasq.conf'? y
[root@rhel-87-nightly NetworkManager-ci]# systemctl restart NetworkManager
[root@rhel-87-nightly NetworkManager-ci]# pgrep -laf dnsmasq
1914 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/NetworkManager/dnsmasq.pid --listen-address=127.0.0.1 --cache-size=400 --clear-on-reload --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d
[root@rhel-87-nightly NetworkManager-ci]# cat << EOF > /etc/NetworkManager/conf.d/90-dns-none.conf
[main]
dns=none
EOF
[root@rhel-87-nightly NetworkManager-ci]# systemctl restart NetworkManager
[root@rhel-87-nightly NetworkManager-ci]# pgrep -laf dnsmasq
1914 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/NetworkManager/dnsmasq.pid --listen-address=127.0.0.1 --cache-size=400 --clear-on-reload --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d
tested using: NetworkManager-1.40.0-2.el8_7.x86_64
The fix works for me, setting Verified:Tested: # grep dns= /etc/NetworkManager/NetworkManager.conf dns=dnsmasq # pgrep dnsmasq -a 11949 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.0.1 --cache-size=400 --clear-on-reload --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d # sed -i 's/dns=dnsmasq/dns=none/' /etc/NetworkManager/NetworkManager.conf # systemctl restart NetworkManager # pgrep dnsmasq -a # 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 (NetworkManager bug fix and enhancement 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/RHBA-2023:2968 |