attachment_create fails on live migration with bfv instance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Unassigned |
Bug Description
While testing live migration with the new v3 cinder api, I found that migrating an instance that was booted from a volume (bfv) fails during pre_live_migration. The problem happens when we are creating a new attachment (attachment_create) to attach the volume on the destination host. The attachment_create fails because the volume's status is 'in-use' and attachment create wants it to be available or downloading.
(This is similar to the reserve issue - https:/
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[[01;31m2017-06-12 14:09:57.141 TRACE oslo_messaging.
^[vailable or downloading[