Issue

• Connectivity of a network Team interface does not always work at boot. When in the non-working state, inspection shows one or more of the team ports have an unexpected MAC address:

  $ ip link | grep team0
  2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master team0 portid state UP mode DEFAULT qlen 1000
      link/ether 52:54:00:99:83:e7 brd ff:ff:ff:ff:ff:ff
  --
  5: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master team0 portid state UP mode DEFAULT qlen 1000
      link/ether d6:cc:8d:b0:7a:a1 brd ff:ff:ff:ff:ff:ff
  --
  7: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master team0 portid state UP mode DEFAULT qlen 1000
      link/ether d6:cc:8d:b0:7a:a1 brd ff:ff:ff:ff:ff:ff
  --
  8: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master team0 portid state UP mode DEFAULT qlen 1000
      link/ether 52:54:00:99:83:e7 brd ff:ff:ff:ff:ff:ff
  --
  11: team0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000
      link/ether 52:54:00:99:83:e7 brd ff:ff:ff:ff:ff:ff
  

• Typically affects systems with more than one team configured and that use NetworkManager.