Comment 1 for bug 1090167

Revision history for this message
John Griffith (john-griffith) wrote :

We must be doing the same sort of testing this week Sam... I have a note to fix this in the SolidFire driver and will need to check the other drivers to make sure this isn't happening.

It seems we assumed if a delete call made it to us that the volume would exist on our back-end systems and we raise. Bad idea, so my approach has bee to remove the raise and instead log an error and move on. It would be nice if we get states implemented and we could use that to determine more appropriately what should be done (raise, log error, nothing etc) but until then I think logging an error is best. For all purposes the volume is deleted as the user requested.