Restarting destination compute manager during resize migration can cause instance data loss
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
jichenjc |
Bug Description
During compute manager startup init_host is called. One of the functions there is to delete instance data that doesn't belong to this host i.e. _destroy_
If at this time a resize migration is taking place and the destination compute manager is restarted it might destroy the resizing instance. Alternatively, if the resize has completed (vm_state = RESIZED) but has not been confirmed/reverted, then a restart of the source compute manager might destroy the original instance.
A similar bug concerning just the migrating state is outlined here: https:/
It was intended to have that fix deal with resize migrating instances as well as those just in the migrating state but as pointed out in a review comment this solution will work for migrating but a fix for resize would require further changes so I have raised this bug to highlight that.
description: | updated |
Changed in nova: | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: compute icehouse-backport-potential |
Changed in nova: | |
assignee: | nobody → jichenjc (jichenjc) |
Changed in nova: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-3 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/101803
Review: https:/