© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
Hi Sean, what backend did you reproduced that? I tried to reproduce with Hitachi HUS driver[1], and as John said, the problem should happen when the backend use the ID to identify the volume in the array, so, as expected (hus driver stores the volume identity in the metadata) it worked well.
But, when I did the same in our NFS and iSCSI backends[2], which use the ID to name the volume in the array, the re-type also worked with no problems as well. After retyping I can access and use the volumes in the new backends.
What I think is happening is that cinder is using the name_id to access the volume which always is updated to the volume name present in the ID.
[1] http://
[2] http://