Description of problem: Setting MACADDR= in the network configuration file for an OVS bridge does not work as expected. While the MAC address will be set initially, any OVS operation that changes *any* aspect of the OVS configuration will revert the MAC address to the one originally allocated to the bridge. Version-Release number of selected component (if applicable): openvswitch-2.0.1-1.fc20.x86_64 How reproducible: Create a configuration file /etc/sysconfig/network-scripts/ifcfg-br-test0 with the following contents: DEVICE=br-test0 DEVICETYPE=ovs TYPE=OVSBridge ONBOOT=yes IPADDR=192.168.17.7 NETMASK=255.255.255.0 OVSDHCPINTERFACES=eth0 MACADDR=c0:ff:ee:ee:ff:0c Bring up the interface: # ifup br-test0 Examine the MAC address: 10: br-test0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default link/ether c0:ff:ee:ee:ff:0c brd ff:ff:ff:ff:ff:ff Make an unrelated OVS change: # ovs-vsctl add-br br-not-important Examine the MAC address on br-test0 and see that it has changed: 10: br-test0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default link/ether d2:2c:53:bb:16:46 brd ff:ff:ff:ff:ff:ff Expected results: I expect the MAC address set in the interface configuration file to stick. Additional info: You can work around this problem right now by adding the following to the interface configuration file: OVS_EXTRA="set bridge br-test0 other-config:hwaddr=$MACADDR" However, I think that this should be handled automatically by ifup-ovs to avoid the surprising behavior demonstrated here.
I submitted a patch for this upstream: http://openvswitch.org/pipermail/discuss/2014-May/014062.html
*** This bug has been marked as a duplicate of bug 1134037 ***