Description of problem: Balloon on VM is re-enabled with every API call. Version-Release number of selected component (if applicable): vt5 How reproducible: 100% Steps to Reproduce: 1. Add VM 2. Edit VM -> Resource Allocation -> Uncheck 'Memory Balloon Device Enabled' 3. Edit VM name via REST or other API curl -X PUT -H "Accept: application/xml" -H "Content-Type: application/xml" -u admin@internal:$pwd --cacert ca.crt -d "<vm><name>foo</name></vm>" https://$engine/api/vms/$vmID Actual results: VM is re-enabled on VM. Expected results: All the settings of VM should stay as before REST API call edit except for name. Additional info: The same behaviour via rhevm-shell. This fix should be backported to rhevm 3.4 as it is causing huge problems with ppc where ballooning is not supported.
Whatever the solution to this issue is, please try to make sure that there is no business logic inside the RESTAPI.
so is this reproducible on 3.4.z engine?
yes, WA for this is to add to every API CALL <ballooning>false<ballooning> In case this is missing in the API call balloon will be reenabled
*** Bug 1153006 has been marked as a duplicate of this bug. ***
verified in vt9
rhev 3.5.0 was released. closing.