Comment 0 for bug 1450649
Revision history for this message
| Sean McGinnis (sean-mcginnis) wrote Retyping to new backend not renaming volume on array | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
When doing a retype volumes are being lost. Cinder calls in to the driver to have a new volume created an the second backend. It then copies the data over from the first backend to the new lun on the second backend. After the migration of the data completes the original lun on the first backend is deleted.
The problem with this is the new volume is given a new ID, but the cinder database keeps the original volume id. There is a missing step where cinder should instruct the driver to update the new volume's ID so that it matches the old deleted volume.
Subsequent calls in to the driver to manipulate the volume fail because cinder still has the old ID but the array only has the new ID.