i am setting the importance to medium as this seams to be quite hard to trigger as all but 1 out of the 10-12 attempts i made failed so i think this will be hit rarely.
when this happens the vm is left in a running state runing on the target host. stopping the vm and starting it restores it to an active state.
http:// paste.openstack .org/show/ 795679/
i was able to repoduce this once on master but not reliably yet.
so im moving this to confimed.
we also have a downstream report of this on train /bugzilla. redhat. com/show_ bug.cgi? id=1850400
https:/
sill at that to the affeted versions
i am setting the importance to medium as this seams to be quite hard to trigger as all but 1 out of the 10-12 attempts i made failed so i think this will be hit rarely.
when this happens the vm is left in a running state runing on the target host. stopping the vm and starting it restores it to an active state.