RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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