live_migration does not perform vif unplugging
Bug #899767 reported by
dan wendlandt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
dan wendlandt | ||
neutron |
Fix Released
|
High
|
dan wendlandt |
Bug Description
Migrated a VM with the command:
sudo nova-manage vm live_migration i-00000011 host2
If we are migrating from host1 to host2, the network devices representing the VM VIF on host1 are not properly destroyed.
This ends up confusing Quantum, as the VM appears to both be in the old and new location simultaneously, leading to incorrect behavior.
Seems like the underlying problem is that vif unplugging usually happens in the driver.destroy() call in the virt layer. However, in the case of live migration (i.e., non block migration), destroy is not called, meaning we have to unplug the vifs explicitly.
Changed in nova: | |
assignee: | nobody → dan wendlandt (danwent) |
Changed in quantum: | |
milestone: | none → essex-2 |
assignee: | nobody → dan wendlandt (danwent) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in nova: | |
status: | New → In Progress |
Changed in nova: | |
milestone: | none → essex-2 |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in quantum: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-2 → 2012.1 |
Changed in quantum: | |
milestone: | essex-2 → 2012.1 |
To post a comment you must log in.
Fix available for review: https:/ /review. openstack. org/#change, 2253,patchset= 1
(isn't jenkins supposed to do this automatically? perhaps my syntax in the commit message is wrong?)