Comment 5 for bug 888649

   Update to describe exact behavior for LVM based driver

    I'm mostly using our own driver in these tests, but I went through the test again using the
    default driver (nova.volume.driver.ISCSIDriver, I believe)

    The behavior of the default driver is slightly different to the behavior I described in the
    original bug report, though it's still broken, I think.

    If I create a volume, then create a snapshot from the volume, and then try
    to delete the base volume, nova-volumes attempts to delete the volume, but
    fails and the volume is left in the stat 'error-deleting'

    In fact I can subsequently delete the snapsnot, but I can't delete the
    volume.

# euca-create-volume -s 1 -z nova
VOLUME vol-0000009d 1 creating (bocktest, None, None, None) 2011-11-15T12:53:25Z
# euca-create-snapshot vol-0000009d
SNAPSHOT snap-00000022 vol-0000009d creating 2011-11-15T12:53:46Z 0%
# euca-delete-volume vol-0000009d
VOLUME vol-0000009d

# euca-describe-volumes
VOLUME vol-00000099 1 nova error (bocktest, stratus10, hostname, None) 2011-11-15T11:37:21Z
VOLUME vol-0000009a 1 nova error_deleting (bocktest, hostname, None, None) 2011-11-15T11:50:06Z
VOLUME vol-0000009d 1 nova error_deleting (bocktest, hostname, None, None) 2011-11-15T12:53:25Z

# euca-delete-volume vol-0000009d
ApiError: Volume status must be available