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):
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
port eth5 is still visible in `teamdctl nm-team config dump`
port eth5 it should no longer be in teamd config
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:
Test case added:
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.