Migrating a volume with multiple attachments only needs to swap once

Bug #1444825 reported by Vincent Hou
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
In Progress
Undecided
Vincent Hou

Bug Description

For migrating an attached volume, we take the nova api update_server_volume to swap the source volume and the destination volume to do the content copy of the volume.

Even if the volume is attached to multiple instances, we only need to call update_server_volume and swap the volume once. Currently there is a for loop in the code to call update_server_volume for all the possible attachments, which seems useless.

The best solution can be pick up the instance, which supports volume swap can call update_server_volume. However, it is not yet supported by nova api, so we can just pick up the first instance from the attachments and run update_server_volume. If update_server_volume is supported, it continues. If not, then migration just fails.

Vincent Hou (houshengbo)
Changed in cinder:
assignee: nobody → Vincent Hou (houshengbo)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/174223

Changed in cinder:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (master)

Change abandoned by Vincent Hou (<email address hidden>) on branch: master
Review: https://review.openstack.org/174223

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.