Comment 11 for bug 1811235

I'm going to mark this low severity because it should be rare to get into this scenario if you're doing a cold migrate. The scheduler should filter out the instance.host unless the allow_resize_to_same_host config option is True (which I guess it is in this case), but even then if you had more compute hosts in your deployment then we should be able to reschedule to another host (unless they are all full). And even if you do hit this, nothing changed with the underlying VM so you can reset the state using this API:

https://developer.openstack.org/api-ref/compute/#reset-server-state-os-resetstate-action

Although that only allows you to set the instance status to active or error (it's already in error status, and the guest isn't running so it's not active either. If you reset to active then the compute manager should automatically stop it via the _sync_power_states periodic task). I'm not sure why we don't allow more sets in the resetState API (like stopped).