Comment 2 for bug 1556717

I am not sure if this is a valid bug, if the instance has already migrated the failure of the action is a valid one and I think we should raise the exception reporting that the instance is not anymore on the source node.
That exception is useful even to catch any mistake made by an operator, for example putting a wrong instance id.
I'd suggest to discuss this bug to see if it is a valid one or if the behaviour is "by design"