The same issue being solved here for 7.7: https://bugzilla.redhat.com/show_bug.cgi?id=1680655

we are going to track this issue via this bug:
https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/beaker-NetworkManager-master-veth-rhel8-upstream/684/artifact/artifacts/FAIL_report_NetworkManager-ci_Test182_teamd_boolean_values_problem.html

ah, wrong link,
https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/beaker-NetworkManager-master-veth-rhel8-upstream/684/artifact/artifacts/FAIL_report_NetworkManager-ci_Test393_default_route_for_vlan_over_team.html

teamd_init() failed.
Failed: Cannot allocate memory
<debug> [1561482210.2741] device[0x559d56486140] (team7): teamd 13852 died with status 256

Log excerpt:

 <debug> [1561482210.3605] device[0x559d56486140] (team7): running: /usr/bin/teamd -o -n -U -D -N -t team7 -gg
 <info>  [1561482210.3630] device (team7): Activation: (team) started teamd [pid 13880]...
 Added loop callback: daemon, 0x555b64a89ce0
 Using team device "team7".
 Using PID file "/var/run/teamd/team7.pid"
 This program is not intended to be run as root.
 <debug> [1561482210.3631] device[0x559d56486140] (team7): activation-stage: complete activate_stage1_device_prepare,v4 (id 1143)
 Added loop callback: libteam_events, 0x555b64a89ce0
 Added loop callback: workq, 0x555b64a89ce0
 Failed to get team runner name from config.
 Using default team runner "roundrobin".
 Failed to set team mode "roundrobin".
 Failed to init runner.
 Removed loop callback: workq, 0x555b64a89ce0
 Removed loop callback: libteam_events, 0x555b64a89ce0
 Removed loop callback: daemon, 0x555b64a89ce0
 teamd_init() failed.
 Failed: Cannot allocate memory

also discussed in https://bugzilla.redhat.com/show_bug.cgi?id=1680655#c4 .

Reassigning to libteam.

FYI, Beniamino's patch has been applied by upstream

commit 5c5e498bff93acec9bdc3b2e3ab5759a97096c50
Author: Beniamino Galvani <bgalvani>
Date:   Tue May 28 10:02:45 2019 +0200

    libteam: set netlink event socket as non-blocking

Vladimir,

With below script wrote by myself,i can't reproduce this bz,can you give me your reproducer?

```
slave1=enp129s0f0np0
slave2=enp129s0f1np1
while :
do
#nmcli con add con-name team0 type team ifname team0 ipv4.method manual ipv4.addr 192.168.1.18/24 connection.autoconnect yes
nmcli con add con-name team0 type team ifname team0
nmcli con add type ethernet con-name $slave1 ifname $slave1 master team0 slave-type team
nmcli con add type ethernet con-name $slave2 ifname $slave2 master team0 slave-type team
nmcli con add type vlan con-name vlan_team0 dev team0 id 3 mtu 1500 ipv4.method manual ipv4.addresses 192.168.3.18/24 ipv4.gateway 192.168.3.1 ipv6.method manual ipv6.addresses 2168::16/64 ipv4.dns 8.8.8.8
nmcli con up team0 || break
nmcli con up $slave1 || break
nmcli con up $slave2 || break
nmcli con up vlan_team0 || break

nmcli con del vlan_team0
nmcli con del $slave1
nmcli con del $slave2
nmcli con del team0
done
```

Liang.

I guess Vladimir found this issue on rhel7 initially. 
He said in comment #1 this is the same issue with bz #1680655.

Because he said in comment #0 the NetworkManager version he used is 1.17.0. But 1.17.0 is a el7 version,not a el8 version.
So maybe Vladimir didn't try to reproduce this issue on rhel8? And he also didn't provide a reproducer for rhel8.

So i think i can use the reproducer described in https://bugzilla.redhat.com/show_bug.cgi?id=1680655#c38 to verify this bz.

And use this reproducer,i can't reproduce this issue on new versions.

while nmcli con add type team  con-name team0 autoconnect no ifname nm-team && nmcli con add type bridge con-name team_br autoconnect no ifname brA ip4 192.168.177.100/24 gw4 192.168.177.1 && nmcli con modify id team0 connection.master brA connection.slave-type bridge && nmcli con up team0 && nmcli con del team0 team_br ;  do :;done

[root@dell-per730-14 ~]# rpm -q libteam
libteam-1.29-1.el8.x86_64
[root@dell-per730-14 ~]# rpm -q NetworkManager
NetworkManager-1.22.0-2.el8.x86_64

set verified.

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:1809