Description of problem: Bug 863105 introduces a regression by loading the slaves configuration from the engine and dismissing the configuration provided by the user, notably using the SDK. For example: Origin configuration: eth0 --- ovirtmgmt eth1 --- net1 eth2 New configuration: eth00 --- ovirtmgmt eth1 --| |---bond0 --- net1 eth2 --| The flat interface list sent to setupNetwork by rest-api contains the 'net1' network attached both to 'et1' and to 'bond0'. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. From setupNetworks dialog attach network 'net1' to eth1 2. Save network configuration (using setupNetworks) 3. Using ovirt-engine-sdk-python send setupNetworks command to configure eth1 bonded with eth2 into bond0 and attach 'net1' to it. Actual results: The command fails with error of network 'net1' is being attached to more than one interface. Expected results: Bond should be created with the network attached to it. Additional info: There are variety of errors that can be created due to the failure, i.e. cannot reuse IP that was defined for a network (if configure using static boot protocol).
Verified on rhevm-3.2.0-8.el6ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0888.html