if we boot a VM form a bad image it will be blocked and end up not having any host.
so if you rescue that with any image you should get a 409 conflict as the VM is not on any host
as i noted in https://bugs.launchpad.net/nova/+bug/2071734/comments/71
and if you do it the other way (boot form a good image and rescue with a blocked one)
ill need to test this again with master on Monday
if we boot a VM form a bad image it will be blocked and end up not having any host. /bugs.launchpad .net/nova/ +bug/2071734/ comments/ 71
so if you rescue that with any image you should get a 409 conflict as the VM is not on any host
as i noted in https:/
and if you do it the other way (boot form a good image and rescue with a blocked one)
rescue fails as i noted in /bugs.launchpad .net/nova/ +bug/2071734/ comments/ 70
https:/
so at least with a quick attempt i didn't reproduce the behavior you said in /bugs.launchpad .net/nova/ +bug/2071734/ comments/ 74
https:/
did you use an image that was in the image cache ?
part of the mitigation of this requires that you first purge any bad images form the image cache on the compute node