When I create localnet network, and mutate the 'physicalNetworkName' is order to use different bridge-mapping, the change doesnt seem to take effect on the underlay.
Traffic keeps going through the interface the previous bridge-mapping points to, instead of the interface the new bridge-mapping I just entered points to.

The setup consist of:

• Additional NICs: eth1, eth2,
• OVS bridges: ovsbr1 connected to eth1, ovsb2 connected to eth2.
• Bridge-mappings: localnet1 points to ovsb1, localnet2 points to ovsbr2.

Create localnet NAD with physicalNetworkName to localnet1
Create two pods on different nodes, one pinging the other.
Tcpdump show traffic goes through eth1 - as expected (localnet1 > ovsbr1 > eth1).
Change the NAD's physicalNetworkName to localnet2
Tcpdump show traffic still goes through eth1 instead if eth2  (localnet2 > ovsbr2 > eth2).

Other observations:

• Restarting pods wont make it work.
• Looking into OVS state (ovs-vsctl show), it seems the patch port to br-int remain on ovsbr1 (ref. by localnet1) instead of exist on ovsbr2 (ref. by localnet2).
• Only after the NAD is re-created changes take affect:
  • The patch-port to br-int is removed from the previous selected OVS bridge and create on the OVS bridge the desired mapping referces to.
  • Tcpdump show traffic goes through eth2 - as desired.
• When the physicalNetworkName change combined with vlan change, changes take affect and traffic goes through the desired NIC.