Fix failed migration so that support can revert resize

Registered by Souvik Basu on 2013-05-22

There are couple of scenarios in which the instance's vm_state and task_state are not in one of the allowed states. For instance the rsync process dies midway due to deployments or compute node restart and never goes to error state. In those cases support is forced to update the db and put the instance and migration to error status so that the revert goes through. The reset-state api only changes the vm state and marks the task state as None. We need to change the migration status to 'finished' for the revert.
We will have to add a new extension to reset the vm_state to 'resized', task state to None and the migration status to 'finished'

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Drafting
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/fix-failed-migration,n,z

Addressed by: https://review.openstack.org/30091
    Support should be able to revert-resize when it fails or hangs

Gerrit topic: https://review.openstack.org/#q,topic:bp/fix-failed-migration,n,z

Addressed by: https://review.openstack.org/30091
    Support should be able to revert-resize when it fails or hangs

If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.