Comment 8 for bug 1450649

@John
In fact those 2 backends are actually in the same storage, but I configured 2 backends on cinder.conf and it seemed to me that the migration occurred as I used a distinct volume_backend_name for each. The operation takes a long time, I can see 'dd' copying the data, and as you can see on [1] after the migration is triggered, cinder list shows 3 volumes, and then, when it is finished, 2, with the same UUID as before. HUS does not use the volume ID to name the volume on storage.

In the second example (migrating v3 to hnas-nfs) the migration also happen (the physical backend are the same but its another protocol). Both backends use the volume ID as volume name and I had no problems to perform other operations after the migration.

I still curious to know what backends this problems is happening and why the problem does not happen with HNAS.