Soft-reboot fails after volume-update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
melanie witt | ||
Ocata |
Fix Committed
|
Undecided
|
melanie witt | ||
Pike |
Fix Committed
|
Undecided
|
Matt Riedemann |
Bug Description
During a volume-update, we don't save the instance XML with the new volume attachment, so soft-reboot fails with:
DEBUG nova.virt.
WARNING nova.virt.
as it can't access the old volume attachment defined in the XML. It falls back on a hard reboot which is like pulling the power cord and can result in file system inconsistencies.
We should save the updated XML to the persistent configuration after updating the volume.
Steps to reproduce:
1. Boot an instance (nova boot --image <image> --flavor <flavor> test0)
2. Create two volumes (cinder create --name A 1, cinder create --name B 1)
3. Attach the first volume to the instance (nova volume-attach test0 <uuid of volume A>)
4. Swap to the second volume (nova volume-update test0 <uuid of volume A> <uuid of volume B>)
5. Try to reboot the instance (nova reboot test0)
Actual result:
Instance fails to soft-reboot and hard reboots instead.
Expected result:
Instance soft-reboots successfully.
Fix proposed to branch: master /review. openstack. org/498983
Review: https:/