Bug 1719318

Summary: [NMCI] route table is sometimes ignored
Product: Red Hat Enterprise Linux 8 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: sushil kulkarni <sukulkar>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: ---CC: atragler, bgalvani, fgiudici, lrintel, rkhan, sukulkar, thaller
Target Milestone: rc   
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.20.0-4.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:30:06 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 2019-06-11 13:54:35 UTC
Description of problem:
when tests were executed in a certain order one of them failed.

Runnig this:
nmcli/./runtest.sh team_in_vlan_restart_persistence  && nmcli//runtest.sh ipv6_routes_with_src  && nmcli/./runtest.sh ipv6_route_set_route_with_tables

lead to the last one failed

Version-Release number of selected component (if applicable):
NM-1-20

Comment 1 Vladimir Benes 2019-06-11 13:59:01 UTC
smaller reproducer:
### start with eth10 disconnected

# ip l set eth10 down
# ip l set eth10 up

# nmcli connection add type  ethernet ifname eth10 ip4 9.9.9.9/32 ipv4.route-table 300 ipv4.route "9.9.9.10"

# sleep 5

# ip r
9.9.9.9 dev eth10 proto kernel scope link src 9.9.9.9 metric 101 
9.9.9.10 dev eth10 proto static scope link metric 101 
# ip r show table 300
#

Comment 4 Vladimir Benes 2019-08-01 13:03:35 UTC
this works well now

Comment 6 errata-xmlrpc 2019-11-05 22:30:06 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, 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-2019:3623