instance corrupted after volume retype
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Lee Yarwood | ||
Queens |
In Progress
|
Undecided
|
Lee Yarwood | ||
Rocky |
In Progress
|
Undecided
|
Lee Yarwood | ||
Stein |
In Progress
|
Undecided
|
Lee Yarwood | ||
Train |
Fix Released
|
Undecided
|
Unassigned | ||
Ussuri |
Fix Released
|
Undecided
|
Unassigned | ||
Victoria |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Description
===========
Following a cinder volume retype on a volume attached to a running instance, the instance became corrupt and cannot boot into the guest operating system any more.
Upon further investigating it seems the retype operation failed. The nova-compute logs registered the following error:
Exception during message handling: libvirtError: block copy still active: domain has active block job
see log extract: http://
Steps to reproduce
==================
I'm not sure how easy this would be to replicate the exact problem.
As an admin user within the project, in Horizon go to Project | Volume | Volume, then from the context menu of the required volume select "change volume type".
Select the new type and migration policy 'on-demand'.
Following this it was reported that the instance was none-responsive, when checking in the console the instance was unable to boot from the volume.
Environment
===========
DISTRIB_ID="OSA"
DISTRIB_
DISTRIB_
DISTRIB_
# nova-manage --version
18.1.1
# virsh version
Compiled against library: libvirt 4.0.0
Using library: libvirt 4.0.0
Using API: QEMU 4.0.0
Running hypervisor: QEMU 2.11.1
Cinder v13.0.3 backed volumes using Zadara VPSA driver
Are users trying to migrate multiple volumes attached to the same instance at the same time?