Comment 16 for bug 1433019

Hi Vincent,

I tried your patch and the patch solved the migration problem. Thanks,
Waiting for your further investigation of this issue.

Test environment & steps

$ cinder service-list
+------------------+--------------------+------+---------+-------+----------------------------+-----------------+
| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+------------------+--------------------+------+---------+-------+----------------------------+-----------------+
| cinder-backup | host1 | nova | enabled | down | 2015-03-18T19:28:18.000000 | - |
| cinder-scheduler | host1 | nova | enabled | up | 2015-03-25T15:40:36.000000 | - |
| cinder-volume | host2@lvmdriver-2 | nova | enabled | up | 2015-03-25T15:40:41.000000 | - |
| cinder-volume | host1@lvmdriver-1 | nova | enabled | up | 2015-03-25T15:40:44.000000 | - |
+------------------+--------------------+------+---------+-------+----------------------------+-----------------+

Env:
  2 x c-vol nodes(apply your patch for both nodes).
  Both backends use lioadm of LVM driver.

  [lvmdriver-1]
  iscsi_helper = lioadm
  volume_group = stack-volumes-lvmdriver-1
  volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver
  volume_backend_name = lvmdriver-1

  [lvmdriver-2]
  iscsi_helper = lioadm
  volume_group = stack-volumes-lvmdriver-2
  volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver
  volume_backend_name = lvmdriver-1

Steps:
1. Create a volume(The volume was created on host1@lvmdriver-1)
2. Attach a volume to a nova instance
3. Migrate a volume from host1@lvmdriver-1 to host2@lvmdriver-1
   $ cinder migrate vol1 host2@lvmdriver-2#lvmdriver-1

And then, the volume migration was succeeded.

Thanks,