Stop/start a KVM instance with volumes attached produces an error state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Vish Ishaya | ||
Essex |
Fix Released
|
High
|
Dave Walker | ||
nova (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned | ||
Quantal |
Fix Released
|
High
|
Unassigned |
Bug Description
When a running instance with an attached volume is stopped and then started, the instance refuses to boot and goes into an error state. This appears to be caused by nova-compute incorrectly building the libvirt.xml file.
2012-06-15 03:54:14 TRACE nova.compute.
A log of the start and the generated libvirt.xml are attached. In particular:
<disk type='block'>
libvirt expects <target dev='vdz' bus='virtio'/>, and refuses to boot otherwise. Issuing a reboot to the instance does not trigger this (and the XML file is not even updated with the volume, presumably because the process is simply given a hard reboot order).
Version: 2012.1-0ubuntu2.2 (with SRU patch from 2012.1-0ubuntu2.3 manually applied)
Related branches
- Chuck Short: Pending requested
-
Diff: 56 lines (+14/-4)3 files modifieddebian/changelog (+8/-0)
debian/control (+6/-3)
debian/nova-console.install (+0/-1)
Changed in nova: | |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: volume |
Changed in nova (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in nova (Ubuntu Precise): | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: rls-q-incoming |
Changed in nova: | |
milestone: | none → folsom-2 |
status: | Fix Committed → Fix Released |
Changed in nova (Ubuntu Quantal): | |
status: | Confirmed → Fix Released |
Changed in nova: | |
milestone: | folsom-2 → 2012.2 |
So I was able to reproduce this in Essex but not folsom. Im thinking that the following commit fixed this:
https:/ /github. com/openstack/ nova/commit/ ae878fc8b9761d0 99a4145617e4a48 cbeb390623
However I dont think its apprioate to backport this fix. So im looking at alternatives.
chuck