Created attachment 1092795 [details]
source host logs

Description of problem:
After put host to local maintenance, agent migrate engine vm, but source host still have engine vm in state down.
Output from source code:

# hosted-engine --vm-status
--== Host 1 status ==--

Status up-to-date                  : True
Hostname                           : rose05.qa.lab.tlv.redhat.com
Host ID                            : 1
Engine status                      : {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "down"}
Score                              : 0
stopped                            : False
Local maintenance                  : True
crc32                              : 08d9a82e
Host timestamp                     : 14834


--== Host 2 status ==--

Status up-to-date                  : True
Hostname                           : cyan-vdsf.qa.lab.tlv.redhat.com
Host ID                            : 2
Engine status                      : {"health": "good", "vm": "up", "detail": "up"}
Score                              : 3400
stopped                            : False
Local maintenance                  : False
crc32                              : 2cb9a39a
Host timestamp                     : 185334

# vdsClient -s 0 list table
489f97db-fd1d-4504-9ce0-f8732d6b57d1  20649  HostedEngine         Down


Version-Release number of selected component (if applicable):
ovirt-hosted-engine-ha-1.3.2.1-1.el7ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Deploy hosted-engine on two hosts
2. Put host with engine vm to local maintenance(hosted-engine --set-maintenance --mode=local)
3. 

Actual results:
engine vm migrate to second host, but first host still have engine vm in state down

Expected results:
engine vm migrate to second host, and no engine vm on first host

Additional info:
Problem in class EngineMigratingAway, because new_data.migration_result have only string "Done", state machine moved to state ReinitializeFSM and not to EngineDown