When trying to create a volume from an image, if the creation of a temporary file in image_conversion_dir fails, up to 3 volumes are created on the backend. (the number of volumes depends on the value of scheduler_max_attempts)
When tested against the SolidFire driver, the volume status goes to 'error'. Cinder however still managed to create 3 volumes on the SolidFire cluster.
This triggers a side-effect where the volume in error can no longer be deleted by the SolidFire driver ; it is now confused by the existence of 3 volumes with the same name on the cluster.
Errors raised by this kind of failure should be handled properly so Cinder does not reschedule the creation of the volume.
When trying to create a volume from an image, if the creation of a temporary file in image_conversio n_dir fails, up to 3 volumes are created on the backend. (the number of volumes depends on the value of scheduler_ max_attempts)
When tested against the SolidFire driver, the volume status goes to 'error'. Cinder however still managed to create 3 volumes on the SolidFire cluster.
This triggers a side-effect where the volume in error can no longer be deleted by the SolidFire driver ; it is now confused by the existence of 3 volumes with the same name on the cluster.
Errors raised by this kind of failure should be handled properly so Cinder does not reschedule the creation of the volume.