Description of problem: requesting to stop vm that is in down state generate and error: 2014-08-18 18:10:05,606 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (ajp-/127.0.0.1:8702-46) Operation Failed: [Cannot stop VM. VM is not running.] 2014-08-18 18:10:05,439 WARN [org.ovirt.engine.core.bll.StopVmCommand] (ajp-/127.0.0.1:8702-46) [d452d96] CanDoAction of action StopVm failed. Reasons:VAR__ACTION__STOP,VAR__TYPE__VM,ACTION_TYPE_FAILED_VM_IS_NOT_RUNNING although the vm is already down, and this is not a real error for the user, its better to just return a message that the vm is already stopped, as for some users, that monitor the log, it may seem there is some issue in the system. Version-Release number of selected component (if applicable): 3.5 How reproducible: always Steps to Reproduce: 1.using rest-api, stop a vm that is Down Actual results: Error in engine.log Expected results: just an 'normal' (green mark) audit log, saying vm is already down, no error.
This is an automated message: This bug should be fixed in oVirt 3.5.1 RC1, moving to QA
oVirt 3.5.1 has been released. If problems still persist, please make note of it in this bug report.