-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-10.0.beta
-
No
-
Low
-
1
-
rhel-net-mgmt
-
ssg_networking
-
3
-
False
-
False
-
-
None
-
NMT SST - 2025Q2
-
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
The teamd service and libteam library were removed in RHEL 10, (as was NetworkManager-team) but NetworkManager still allows a team device to be configured.
I configured a team using nmcli and saw no errors when configuring it, but when I tried to bring it up it complains there are no plugins (which is expected).
It is also listed as a connection.type in man nmcli.
What is the impact of this issue to you?
Customers may assume that teaming should work and be supported in RHEL 10 due to it being an option. This has the potential to create more support cases and/or Jiras being filed.
Please provide the package NVR for which the bug is seen:
NetworkManager-1.51.90-2.el10.x86_64
How reproducible is this bug?:
100%
Steps to reproduce
root@rhel10-beta:~# nmcli con add type team ifname team0 con-name team0 Connection 'team0' (e8beecc3-91f7-4db9-a8c9-4e810c173248) successfully added. root@rhel10-beta:~# nmcli c s NAME UUID TYPE DEVICE enp1s0 ccddc672-70c1-31a0-bf6f-4ea0c4dfb85b ethernet enp1s0 lo 1c0fb33b-8dbe-4b48-bf69-80e8fbb57c37 loopback lo team0 e8beecc3-91f7-4db9-a8c9-4e810c173248 team -- root@rhel10-beta:~# nmcli con up team0 Error: Connection activation failed: NetworkManager plugin for 'team' unavailable
Expected results
That team* types are not an option in RHEL 10's NetworkManager
Actual results
A team device is created, but not able to be used.