Bug 2189247
| Summary: | Reapply on disabled ipv6 will cause auto ipv4 lose DNS nameserver | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Gris Ge <fge> | ||||
| Component: | NetworkManager | Assignee: | Wen Liang <wenliang> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Matej Berezny <mberezny> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 9.2 | CC: | bgalvani, bnemec, lrintel, rkhan, sfaye, sukulkar, thaller, till, vbenes, wenliang | ||||
| Target Milestone: | rc | Keywords: | Reopened, Triaged, ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | NetworkManager-1.43.5-1.el9 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 2219847 (view as bug list) | Environment: | |||||
| Last Closed: | 2023-11-07 08:38:04 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 2219847 | ||||||
| Attachments: |
|
||||||
|
Description
Gris Ge
2023-04-24 14:07:35 UTC
Wen, I headerd, you were able to reproduce this issue? Could you explain in detail how to reproduce it. Or attach a reproducer script. Or write a NM-ci test (choose whatever approach you want). Also, to my understanding you identified https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/0a02995175e06e62924705393121a1c5efc3822d as the fix? In that case, it is fixed in upstream 1.43.5+, 1.42.6+, 1.40.18+. It is also fixed in rhel-9.3 package NetworkManager-1.43.5-1.el9. As of now, it is not yet fixed in latest rhel-9.2, or latest rhel-8. (In reply to Thomas Haller from comment #6) > Wen, I headerd, you were able to reproduce this issue? > > Could you explain in detail how to reproduce it. Or attach a reproducer > script. Or write a NM-ci test (choose whatever approach you want). > > > Also, to my understanding you identified > > > https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/ > 0a02995175e06e62924705393121a1c5efc3822d > > as the fix? > > > In that case, it is fixed in upstream 1.43.5+, 1.42.6+, 1.40.18+. > It is also fixed in rhel-9.3 package NetworkManager-1.43.5-1.el9. > As of now, it is not yet fixed in latest rhel-9.2, or latest rhel-8. I discussed this bug with bgalvani, the upstream nm-1-40 and nm-1-42 branches already had that commit and there was no customer request for backporting into rhel-9.2/rhel-8.8. About the steps to reproduce the bug: 1. I used the nm-in-container.sh script and added the eth1 interface 2. nmcli connection add type ethernet ifname eth1 con-name eth1+ ipv6.method manual ipv6.addresses $someaddr ipv6.dns $somedns 3. nmcli connection up eth1+ 4. nmcli | grep -A10 "DNS configuration:" (In this case, you should be able to see some IPv4 and IPv6 DNS) 5. nmcli connection modify eth1+ -ipv6.addresses $someaddr -ipv6.dns $somedns ipv6.method disabled (Remove the IPv6 addresses and DNS, and set the Ipv6 method into disabled) 6. nmcli device reapply eth1+; nmcli | grep -A10 "DNS configuration:" (The expected behavior is that the IPv4 DNS is not removed, but if the bug persists, then the IPv4 DNS is removed) Hi Wen, Please prepare a scratch build of 9.2 for Ben Nemec to try out. (In reply to Gris Ge from comment #12) > Hi Wen, > > Please prepare a scratch build of 9.2 for Ben Nemec to try out. Sure, I will do it! 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:6585 |