I think there is a valid case for doing block migrate with a cinder volume attached to an instance:
* Cloud isn't using a shared filesystem for ephemeral storage
* Instance is booted from an image, and a volume is attached afterwards. An admin wants to take the box the instance is running on offline for maintenance with a minimal impact to the instances running on it.
The 'fix' was a a workaround not not an actual fix. It sounds like a fix is needed in libvirt first.
I think there is a valid case for doing block migrate with a cinder volume attached to an instance:
* Cloud isn't using a shared filesystem for ephemeral storage
* Instance is booted from an image, and a volume is attached afterwards. An admin wants to take the box the instance is running on offline for maintenance with a minimal impact to the instances running on it.
The 'fix' was a a workaround not not an actual fix. It sounds like a fix is needed in libvirt first.
http:// lists.openstack .org/pipermail/ openstack- dev/2015- March/059324. html