Bug 2006677

Summary: [NMCI] ipv4_dns-search_remove test failure
Product: Red Hat Enterprise Linux 8 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: Lubomir Rintel <lrintel>
Status: CLOSED ERRATA QA Contact: Vladimir Benes <vbenes>
Severity: unspecified Docs Contact:
Priority: high    
Version: 8.4CC: bgalvani, ferferna, fge, lrintel, rkhan, sukulkar, till
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.36.0-0.2.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-10 14:54:14 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:

Description Vladimir Benes 2021-09-22 07:14:45 UTC
Description of problem:
we can see a race when a profile is up (with ipv4.may-fail no) but we cannot ping domain for a short time as probably DNS records are not done properly.

    @con_ipv4_remove @eth0
    @ipv4_dns-search_remove
    Scenario: nmcli - ipv4 - dns-search - remove dns-search
    * Add a new connection of type "ethernet" and options "ifname eth0 con-name con_ipv4 ipv4.may-fail no ipv4.dns-search google.com"
    * Modify connection "con_ipv4" changing options "ipv4.dns-search ''"
    * Bring "up" connection "con_ipv4"
    Then Domain "google.com" is not set
    Then Unable to ping "maps"
    Then Ping "maps.google.com"
 


Version-Release number of selected component (if applicable):
NetworkManager-1.32.10-2.el8.x86_64

How reproducible:
once in 20 cycles

Steps to Reproduce:
1. download NMCI tests
2. test=ipv4_dns-search_remove; a=0; while ./test_run.sh $test; do :;((a++)); echo "ATTEMPT $a"; if [ $a -eq 100 ]; then break; fi ; done

Actual results:
fail in less than 100

Expected results:
should end after 100 cycles

Additional info:

Comment 5 Vladimir Benes 2021-11-16 13:49:24 UTC
test executed 200 times w/o any issue on main copr build
NetworkManager-1.33.4-29390.copr.3bc14e3e88.el8.x86_64

Comment 13 errata-xmlrpc 2022-05-10 14:54:14 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 (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/RHEA-2022:1985