Make evacuate leave a record for the source compute host to process
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Low
|
Unassigned |
Bug Description
https:/
commit d9c696acf85a00f
Author: Dan Smith <email address hidden>
Date: Thu May 14 15:52:05 2015 -0700
Make evacuate leave a record for the source compute host to process
This makes the evacuate process leave a record in the database about the
evacuation, and from what host it was being performed. Now, the compute
manager will use that breadcrumb trail to decide whether it should delete
locally-running instances, instead of just the hostname mismatch.
Since this does a query by migration_type, I added a unit test to the
test_db_api module to prove this actually works.
DocImpact: Deprecates the workarounds/
Related to blueprint robustify-
Closes-Bug: #1471887
Change-Id: I972c224dfb954a
Changed in openstack-manuals: | |
assignee: | nobody → Bevis Chen (bevis-c) |
Changed in openstack-manuals: | |
status: | In Progress → Triaged |
assignee: | Gauvain Pocentek (gpocentek) → nobody |
Changed in openstack-manuals: | |
milestone: | liberty → mitaka |
Changed in openstack-manuals: | |
milestone: | mitaka → newton |
Changed in openstack-manuals: | |
status: | Triaged → Fix Released |
milestone: | newton → mitaka |
Autogenerate- config- docs should handle this