Description of problem:
We created a new VM and wanted to install OS on it. So it was started

2014-10-23 15:16:31,213 - MainThread - vms - DEBUG - Action request content is --  url:/api/vms/c7141d36-6d6a-4700-991f-89377e849d26/start body:<action>
    <async>false</async>
    <grace_period>
        <expiry>10</expiry>
    </grace_period>
    <vm>
        <os>
            <boot dev="hd"/>
            <boot dev="network"/>
        </os>
    </vm>
</action>

Response from RHEV-M:
2014-10-23 15:19:32,265 - MainThread - api_utils - ERROR - Failed to syncAction element:
	Status: 400
	Reason: Bad Request
	Detail: [Network error during communication with the Host.]


Despite that, VM was actually started. I cannot find any information about another attempt of starting this machine and it is hardly possible someone did it - it was during automated tests, I just monitored it and a while (10 minutes?) after that error I noticed it, logged into RHEV-M and saw that this VM is up and running.


Version-Release number of selected component (if applicable): vt7


How reproducible: so far happened once


Steps to Reproduce:
1. create a new vm
2. start it

Actual results:
RHEV-M responded with an error, but VM is booted


Expected results:
RHEV-M should either not respond with an error, or not start VM.


Additional info: