Hide Forgot
Description of problem: Deactivation of slave connection (having team-port.config set), does not propagate to teamd, it is still visible with `teamdctl <dev> config dump`. Version-Release number of selected component (if applicable): NetworkManager-1.20.0-3.el8.x86_64 NetworkManager-team-1.20.0-3.el8.x86_64 libteam-1.28-4.el8.x86_64 teamd-1.28-4.el8.x86_64 How reproducible: always Steps to Reproduce: 1. nmcli con add type team ifname nm-team con-name team0 team.runner activebackup ip4 172.20.1.3/24 2. nmcli con add type ethernet ifname eth5 master nm-team con-name team0.0 team-port.prio -10 team-port.sticky true 3. nmcli con up id team0.0 # port eth5 is visible in `teamdctl nm-team config dump` 4. nmcli con down id team0.0 Actual results: port eth5 is still visible in `teamdctl nm-team config dump` Expected results: port eth5 it should no longer be in teamd config
Fix at: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/293 Note that we can set an empty configuration for the port, but it's not possible to completely remove the node from the configuration because of a limitation in the teamd API: { "device": "nm-team", "mcast_rejoin": { "count": 1 }, "notify_peers": { "count": 1 }, "ports": { "eth5": {} }, "runner": { "name": "activebackup" } }
Test case added: team_port_multiple_slaves
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-2020:1847