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:

After performing "sudo ip li set bond0 down" on team interface it disappears, 'sudo ip li' doesn't show it.

Version-Release number of selected component (if applicable):
libteam version: 1.27-10.el8 

How reproducible:
eno2 is some NIC on the RHEL8 host:
$ sudo ethtool -i eno2
driver: tg3
version: 3.137
firmware-version: FFV7.10.0 bc 5720-v1.36
expansion-rom-version: 
bus-info: 0000:03:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

The following steps lead to the described problem:

$ sudo /usr/bin/teamd -t bond0 -d -g -c '{"device":"bond0", "runner":{"name":"activebackup"}}'
Using team device "bond0".
Using PID file "/var/run/teamd/bond0.pid"
This program is not intended to be run as root.

// 'sudo ip li' now shows bond0 interface

$ sudo ip li set bond0 up
$ sudo /usr/bin/teamdctl bond0 port add eno2
$ sudo ip li set bond0 down

// And now bond0 disappears, 'sudo ip li' doesn't show it
// 'sudo ip li set bond0 up' returns 'Cannot find device "bond0"'

Expected results:
On RHEL7 team interface can be set down without deleting, and further 'sudo ip li set bond0 up' works without problems.

Can you stop NM (# systemctl stop NetworkManager) and try?

Thanks.

With stopped NM there is no such problem,  'sudo ip li' shows bond0 interface after 'sudo ip li set bond0 down'.

I can add 2 points to Yurij'd report (I'm talking about the same machines!):
1.
cat /etc/sysconfig/network-scripts/ifcfg-bond0
NAME=bond0
NM_CONTROLLED=no

2. If we use bonding, then "ip li set bond0 down" does not remove the interface; it brings the interface down.  If we use teaming, then the interface is completely removed when we bring it down on RHEL8.

Hi,

this is a duplicate of bug 1693142, which is fixed upstream in NetworkManager. The fix will be in RHEL 8.1.

*** This bug has been marked as a duplicate of bug 1693142 ***