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:

There is a regression caused by upstream commit:
a3cf54617487a05dc1666a856deace46f9c2df5a
It causes that when using take-over mode, there is impossible to remove a port using ctl iface (teamdctl for example).

Version-Release number of selected component (if applicable):
libteam-1.9-15.el7

How reproducible:
always

Steps to Reproduce:
1. teamd -d -t team0
2. teamdctl team0 p a ens7
3. teamdctl team0 p d ens7

Actual results:
ip link shows "master team0" for ens7"

Expected results:
ip link does not show "master team0" for ens7"

Additional info:
NA

The mentioned commit also introduces possible use after free situation. Fix it in this bz as well.

Upstream fix:

https://github.com/jpirko/libteam/commit/6c8d2e8102ea5613acdf5f01d37346d3d059ff53

*** Bug 1125292 has been marked as a duplicate of this bug. ***

Verified on libteam-1.14-1.el7.x86_64

[root@hp-dl388g8-14 ~]# rpm -q libteam
libteam-1.14-1.el7.x86_64

[root@hp-dl388g8-14 ~]# teamd -d -t team0
[root@hp-dl388g8-14 ~]# teamdctl team0 port add ens1f2
[root@hp-dl388g8-14 ~]# ip link show ens1f2
4: ens1f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master team0 state UP mode DEFAULT qlen 1000
    link/ether 00:1b:21:85:84:02 brd ff:ff:ff:ff:ff:ff
[root@hp-dl388g8-14 ~]# teamdctl team0 port remove ens1f2
[root@hp-dl388g8-14 ~]# ip link show ens1f2
4: ens1f2: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000
    link/ether 00:1b:21:85:84:02 brd ff:ff:ff:ff:ff:ff

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://rhn.redhat.com/errata/RHBA-2015-0332.html