DescriptionBeniamino Galvani
2019-05-20 13:30:48 UTC
+++ This bug was initially created as a clone of Bug #1693142 +++
Description of problem:
NetworkManager kills teamd on assumed device when the link goes down.
Version-Release number of selected component (if applicable):
NetworkManager-1.14.0-14.el8
How reproducible:
always
Steps to Reproduce:
setenforce permissive
ip link add veth0 type veth peer name veth1
teamd -d -c "{\"device\":\"team0\",\"runner\":{\"name\":\"lacp\"},\"link_watch\":{\"name\":\"ethtool\"},\"ports\":{\"veth0\":{}}}"
ip link set team0 up; ip link set team0 down; sleep 2
ip link set team0 up; ip link set team0 down; sleep 2
ps aux |grep teamd
Actual results:
NM kills teamd
<debug> [1553674909.1709] device[0xa794a0] (team0): deactivating device (reason 'connection-assumed') [41]
<debug> [1553674909.1711] device[0xa794a0] (team0): running: /usr/bin/teamd -k -t team0
Expected results:
teamd is not killed
--- Additional comment from Beniamino Galvani on 2019-05-20 15:29:45 CEST ---
Upstream fix:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/008a4b4215dcce40345b2c372ffc8cfd0d388fa5
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:2302