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

Posted to issues@cloudstack.apache.org by "Remi Bergsma (JIRA)" <ji...@apache.org> on 2014/04/30 14:35:15 UTC

[jira] [Created] (CLOUDSTACK-6540) API: add listOrphanedSnapshots() call

Remi Bergsma created CLOUDSTACK-6540:
----------------------------------------

             Summary: API: add listOrphanedSnapshots() call
                 Key: CLOUDSTACK-6540
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6540
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: API
    Affects Versions: 4.3.0
            Reporter: Remi Bergsma


When a volume is migrated to another primary storage, its snapshots disappear from the UI as they are linked to the now expunged volume. The snapshot itself is not marked as deleted in the database, so it stays there.

A listall=true displays them all, but there is no way to tell if the snapshot is still linked to a volume that is still active.

When I know the name of the volume, I can use a keyword search like this:

> list snapshots listall=true filter=name,created,volumeid keyword=ROOT-18202
count = 3
snapshot:
+------------------------------------+--------------------------+--------------------------------------+
|                name                |         created          |               volumeid               |
+------------------------------------+--------------------------+--------------------------------------+
| centos01_ROOT-18202_20140430110253 | 2014-04-30T13:02:53+0200 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 |
| centos01_ROOT-18202_20140429101022 | 2014-04-29T12:10:22+0200 | 3788e908-eb75-4063-8116-ec9812d3fb95 |
| centos01_ROOT-18202_20140429095746 | 2014-04-29T11:57:46+0200 | 166f7545-33e2-423a-b900-3f3cea64a868 |
+------------------------------------+--------------------------+--------------------------------------+

But there is no way to list all the orphaned ones. To garden those, please add an api call that lists all snapshots that are linked to expunged volumes. One can use its output to delete the snapshots.




--
This message was sent by Atlassian JIRA
(v6.2#6252)