Comment 5 for bug 1663513

Hi all,

To fix this issue masakari will reset the vm_state of an instance and then will try to stop and start it.
So at the end instance will be in ‘active' state which is not as expected from user's point of view.

For example, if user has paused an instance purposely and after some time qemu process is killed due to some reason, then masakari will stop and start that instance and the instance will be in ‘active’ state at the end. Later when user come back then he will find that instance is active and he/she won't be having any idea what has happened exactly.

User must be expecting the consistency between the vm_state before recovery and vm_state after recovery.

IMO masakari should maintain the consistency between the vm_state before recovery and vm_state after recovery.

For example, if the instance was in 'paused' vm_state then after recovering the instance qemu process by starting that instance again, masakari should pause that instance again.

Please suggest your opinion about this.