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.
Conflicts: nova/conductor/manager.py
NOTE(mriedem): The conflict is due to not having change
I6590f0eda4ec4996543ad40d8c2640b83fc3dd9d in Ocata.
Change-Id: I06d78c744fa75ae5f34c5cfa76bc3c9460767b84
Closes-Bug: #1713783
(cherry picked from commit a8ebf5f1aac080854704e27146e8c98b053c6224)
(cherry picked from commit a3f286f43d866cd343d26d9bafadecab1c225e4b)
Reviewed: https:/ /review. openstack. org/518733 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=604954a70a5 dbf6a1bf79d8b67 e8d92c2bf46386
Committed: https:/
Submitter: Zuul
Branch: stable/ocata
commit 604954a70a5dbf6 a1bf79d8b67e8d9 2c2bf46386
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.
Conflicts:
nova/ conductor/ manager. py
NOTE(mriedem): The conflict is due to not having change ec4996543ad40d8 c2640b83fc3dd9d in Ocata.
I6590f0eda4
Change-Id: I06d78c744fa75a e5f34c5cfa76bc3 c9460767b84 54704e27146e8c9 8b053c6224) 343d26d9bafadec ab1c225e4b)
Closes-Bug: #1713783
(cherry picked from commit a8ebf5f1aac0808
(cherry picked from commit a3f286f43d866cd