Comment 2 for bug 1450649

Sean, what kind of back-ends did you use?

I have done some tests with LVM and Storwize V7000.
When I retyped a volume from LVM to Storwize V7000.
The database record ended up with the following:
+------------------------------- -------+--------------------------------------+
| id | _name_id |
+------------------------------ --------+--------------------------------------+
| 90f8ed5c-177f-4eee-acd7-1094ba786077 | 02d59537-7227-4a97-822f-a9510aca25a9 |
+---------------------------- ----------+------------------ --------------------+

_name_id is used to map the cinder volume id and the back-end volume id. They can be different for sure. If these two volume IDs are the same, the _name_id will be NULL. I guess this issue has already been taken care of in the retype code. And I can delete the new created volume with the old volume id, which is expected behavior.

I need folks to help me with more tests. Try retyping between other two back-ends and feed back your results.