Description of problem: If the updated attachment/bond is identical to the original one- setup networks should ignore it. This fix will fix the following bugs- 1. Opening the edit dialog of "out-of-sync" network and clicking ok-> then clicking ok in the setup networks window. Since the ui adds the attachment to the params even if no change was done- the result is- can do action of "editing out-of-sync network is not permitted". Although no change was done. Fixing the engine side should be enough. The engine should ignore this attachment. 2. Sending setup networks command with the existing attachments/bonds as the parameters. Result- setup network is invoked on the host although no changes are needed. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
This request has been proposed for two releases. This is invalid flag usage. The higher numbered release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA
Closing old bugs. In case still happens, pls reopen.