OpenStack Compute (nova)

  1. Series pike
  2. Bug #1713783
  3. Comment #38

Comment 38 for bug 1713783

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix merged to openstack/nova (9.0/mitaka)

Reviewed: https://review.fuel-infra.org/40164
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka

Commit: 171d726d401dcbb75e3cfff5c3f777e3d68ace2d
Author: Előd Illés <email address hidden>
Date: Mon Mar 25 17:27:27 2019

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
I6590f0eda4ec4996543ad40d8c2640b83fc3dd9d in Ocata.

Change-Id: I06d78c744fa75ae5f34c5cfa76bc3c9460767b84
Closes-Bug: #1713783
(cherry picked from commit a8ebf5f1aac080854704e27146e8c98b053c6224)
(cherry picked from commit a3f286f43d866cd343d26d9bafadecab1c225e4b)