Bug 1888229

Summary: we need to clean dns cache when bringing down connection
Product: Red Hat Enterprise Linux 8 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: Thomas Haller <thaller>
Status: CLOSED ERRATA QA Contact: Vladimir Benes <vbenes>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.3CC: acardace, atragler, bgalvani, lrintel, rkhan, sukulkar, till
Target Milestone: rcKeywords: Triaged
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.30.0-0.1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 13:29:43 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 Flags
Reproducer none

Description Vladimir Benes 2020-10-14 12:59:01 UTC
Description of problem:
after running 
    @con_ipv6_remove @eth0
    @ipv6_dns_manual_IP_with_manual_dns
    Scenario: nmcli - ipv6 - dns - method static + IP + dns
     * Add a new connection of type "ethernet" and options "ifname eth10 con-name con_ipv6 ipv4.may-fail no ipv6.method static ipv6.addresses 2001::1/126 ipv6.gateway 4000::1 ipv6.dns '4000::1, 5000::1'"
    Then Nameserver "4000::1" is set in "45" seconds
    Then Nameserver "5000::1" is set
    Then Nameserver "10." is set in "45" seconds

I can still see 

Link 158 (eth3)
      Current Scopes: none   
DefaultRoute setting: no     
       LLMNR setting: yes    
MulticastDNS setting: no     
  DNSOverTLS setting: no     
      DNSSEC setting: no     
    DNSSEC supported: no     
         DNS Servers: 4000::1
                      5000::1

in resolvectl even if the eth3 profile is down, shouldn't this be cleaned? 

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

Comment 1 Beniamino Galvani 2020-10-23 13:45:56 UTC
Hi Vladimir, I can't reproduce the problem with NM 1.26.4. Can you please attach logs? Thanks!

Comment 2 Beniamino Galvani 2020-10-27 15:29:41 UTC
Created attachment 1724550 [details]
Reproducer

Comment 10 Vladimir Benes 2020-11-30 16:47:48 UTC
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/680

passing on all arches

Comment 11 Vladimir Benes 2020-11-30 17:30:09 UTC
ehm, s390x is not passing.. moving back to assigned

Comment 15 Vladimir Benes 2020-12-15 17:44:18 UTC
Now passing on all arches!

Comment 17 errata-xmlrpc 2021-05-18 13:29:43 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 (Moderate: NetworkManager and libnma security, 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/RHSA-2021:1574