This bug has been copied from bug #1433303 and has been proposed
to be backported to 7.3 z-stream (EUS).
* Add a new connection of type "team" and options "con-name team0 ifname nm-team"
* Add a new connection of type "team-slave" and options "con-name team0.0 ifname eth10 master nm-team"
* Add a new connection of type "vlan" and options "con-name team0.1 dev nm-team id 1 mtu 1500 ipv4.method manual ipv4.addresses 192.168.168.16/24 ipv4.gateway 192.168.103.1 ipv6.method manual ipv6.addresses 2168::16/64 ipv4.dns 126.96.36.199"
When "3" is visible with command "ip r |grep nm-team.1 |wc -l" in "2" seconds
* Execute "for i in `seq 1 6`; do ip link set nm-team addr 00:00:11:22:33:$i; done"
Then "3" is visible with command "ip r |grep nm-team.1 |wc -l"
still fails with incorrect device route without metric
[root@qe-dell-ovs5-vm-57 ~]# ip r
default via 10.16.135.254 dev eth0 proto static metric 100
default via 10.16.135.254 dev nm-team proto static metric 350
default via 192.168.103.1 dev nm-team.1 proto static metric 400
10.16.134.0/23 dev eth0 proto kernel scope link src 10.16.134.63 metric 100
10.16.134.0/23 dev nm-team proto kernel scope link src 10.16.135.61 metric 350
192.168.103.1 dev nm-team.1 proto static scope link metric 400
192.168.168.0/24 dev nm-team.1 proto kernel scope link src 192.168.168.16
192.168.168.0/24 dev nm-team.1 proto kernel scope link src 192.168.168.16 metric 400
comment to the other NM bugzilla, sorry, moving back to ON_QA
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.