When engine looses connectivity with vdsm host state do not change to Connecting and Non-Operational.
Steps to Reproduce:
1. Install new host using jsonrpc (check that host is in 'UP' state)
2. stop vdsm
3. Check that host state hasn't changed.
The host state should change to Connection and later to Non-Operational state.
Host state changes as descirbed above.
Marking as verified.
I installed new Host with json-rpc (status 'Up') and killed vdsm and supervdsmServer. Engine reacted to this after a minute or so, and set the status of the Host to 'Connecting'. The same can be found in engine.log. In engine events I can see message 'Host Host is non responsive.', which presents a bit of inconsistency. Almost immediately after Engine set the status to 'Connecting', it started vdsm and supervdsmServer on the Host, and after approx. 20 minutes the Engine set the status of the Host to 'Up'.
I'm marking this as verified, because Engine changes Host state as it should.
oVirt Engine Version: 3.5.0-0.0.master.20140821064931.gitb794d66.el6
oVirt 3.5 has been released and should include the fix for this issue.