Thanks Jiri
Weird thing is that teamd is started and killed at the very second. I
suspect NM from doing this. Maybe you have some teamd connection in NM?
What "nmcli con" command says?
I checked 'nmcli connection' and recall no mention of a new team device there.
Although it does correctly report details of a new team device when if
I create it with nmcli.
Weird indeed. Feel free to cc NM people/maling-list.
This is a regression from F20, so I opened a NetworkManager bug :
https://bugzilla.redhat.com/show_bug.cgi?id=1172734