Description of problem:

The customer is configuring LACP bonds. But this happens with active/backup as well. They noticed that the bonding vlan devices MAC address changes after adding an ip address or rebooting to some random MAC address. This causes the kernel to arp and apparently affected their switches which resulted in poor performance. Although we do not have the details of that. They worked around this by subsequently adding and MAC address as follows. 

nmcli connection modify "bond0.694" "802-3-ethernet.cloned-mac-address" `/sbin/ifconfig bond0 | grep ether | awk '{print $2}'`  
nmcli connection modify "bond0.692" "802-3-ethernet.cloned-mac-address" `/sbin/ifconfig bond0 | grep ether | awk '{print $2}'` 

Version-Release number of selected component (if applicable):

RHEL7.1/bonding/vlan/NetworkManager

3.10.0-229.14.1.el7.x86_64

How reproducible:

I think I can reproduce it as follows. 

Steps to Reproduce:

1. On a RHEL7.1 system:

# nmcli connection add type bond con-name bond0 ifname bond0 mode active-backup
# nmcli connection add type bond-slave con-name eno4 ifname eno4 master bond0

2. Now add the vlan device:

# nmcli connection add type vlan con-name bond0.692 ifname bond0.692 dev bond0 id 692

# ip addr will show that the MAC address is the same as bond0/eno4 for bond0.692, all good so far.

3. Reboot or reload the bonding driver. 

nmcli net off ; modprobe -r bonding ; nmcli net on

and "ip addr" will show that a random MAC address has been assigned to bond0.692. This is where the problems start.

Actual results:

Vlan bond0.692 gets a random MAC address. This affects the switches when it arps.

Expected results:

Get the same MAC address for bond0.692 as the bond0/eno4 interface as per when it was initially configured.

At this stage I am not sure whether this is due to NetworkManager or the bonding driver. For the meanwhile adding as NetworkManager.