Description of problem: Let's say that we configure networkA as a non-VM, vlanned network with mtu 2000 over bond0. After that, we decide to use bond0 for another non-VM vlanned networkB with mtu 1600. The problem is that if the bonding options are different the bond will have to be reconfigured and the mtu of the bond, that should continue to be 2000 will be overriden with the 1600 value. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. ip link add dummy_42 && ip link add dummy_43 2.vdsClient -s 0 setupNetworks networks='{kaboom:{mtu:2200,bonding:bond14,vlan:44}}' bondings='{bond14:{nics:dummy_42+dummy_43,mode:4}}' 3.vdsClient -s 0 setupNetworks networks='{boom:{mtu:2500,bonding:bond14,vlan:45}}' bondings='{bond14:{nics:dummy_42+dummy_43,mode:3}}' 4. ip link show dev bond0 Actual results: the bond reports mtu 1600 Expected results: the bond reports mtu 2000 Additional info:
The steps above are wrong, the bug only happens when it is done in a single setupNetworks command and the python dictionary order happens to make the bigger mtu network be configured before the smaller mtu network.
This is an automated message oVirt 3.4.1 has been released: * should fix your issue * should be available at your local mirror within two days. If problems still persist, please make note of it in this bug report.