You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2015/12/08 10:27:10 UTC

[jira] [Created] (CLOUDSTACK-9119) issues with volumes in Expunged state but not removed

Wei Zhou created CLOUDSTACK-9119:
------------------------------------

             Summary: issues with volumes in Expunged state but not removed
                 Key: CLOUDSTACK-9119
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9119
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
            Reporter: Wei Zhou
            Assignee: Wei Zhou


sometimes the volume is Expunged but not removed from db.

step to reproduce it:
(1) create a vm or create/attach a volume
(2) download volume
(3) expunge the vm, or detach and removed the volume

in this case, the volume will be expunged from primary storage, but not removed from database, because a snapshot of volume still exist in secondary storage (when we download the volume).

we need to fix the issuse related to this case:
(1) resource count of volume and primary storage should not count the Expunged volume
(2) delete a Expunge volume (disabled it, or remove it from secondary storage ?)
(3) auto-delete the volume from database if the download url are cleaned and files on secondary storage are removed 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)