When evacuation fails with NoValidHost, the migration status remains
'accepted' instead of 'error'. This causes problem in case the compute
service starts up again and looks for evacuations with status 'accepted',
as it then removes the local instances for those evacuations even though
the instance was never actually evacuated to another host.
Change-Id: I06d78c744fa75ae5f34c5cfa76bc3c9460767b84
Closes-Bug: #1713783
(cherry picked from commit a8ebf5f1aac080854704e27146e8c98b053c6224)
Reviewed: https:/ /review. openstack. org/504979 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=a3f286f43d8 66cd343d26d9baf adecab1c225e4b
Committed: https:/
Submitter: Jenkins
Branch: stable/pike
commit a3f286f43d866cd 343d26d9bafadec ab1c225e4b
Author: Előd Illés <email address hidden>
Date: Wed Aug 30 16:54:36 2017 +0200
Set error state after failed evacuation
When evacuation fails with NoValidHost, the migration status remains
'accepted' instead of 'error'. This causes problem in case the compute
service starts up again and looks for evacuations with status 'accepted',
as it then removes the local instances for those evacuations even though
the instance was never actually evacuated to another host.
Change-Id: I06d78c744fa75a e5f34c5cfa76bc3 c9460767b84 54704e27146e8c9 8b053c6224)
Closes-Bug: #1713783
(cherry picked from commit a8ebf5f1aac0808