You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sangeetha Hariharan (JIRA)" <ji...@apache.org> on 2013/05/23 02:05:20 UTC
[jira] [Created] (CLOUDSTACK-2635) Object_Store_Refactor -
Snapshots - When snapshots get deleted , they are not marked as "Removed"
in snapshots table.
Sangeetha Hariharan created CLOUDSTACK-2635:
-----------------------------------------------
Summary: Object_Store_Refactor - Snapshots - When snapshots get deleted , they are not marked as "Removed" in snapshots table.
Key: CLOUDSTACK-2635
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2635
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Build from object_store
Reporter: Sangeetha Hariharan
Fix For: 4.2.0
Object_Store_Refactor - Snapshots - When snapshots get deleted , they are not marked as "Removed" in snapshots table
1.Deploy a VM using the Default CentOS Template.
2.Create a Volume.
3.Attach the Volume to the VM deployed in Step 1.
4.Log into the VM and create a ext3 file system on the Data Disk.
5.Mount the Data Disk.
6.Create a File with content on the Data Disk
7.Create a Snapshot of the Data disk.
8.Delete the Snapshot.
After successful deletion of snapshots , the "removed" column in snapshot is not updated.
So we still see the snapshots being listed in "Destroyed" state when listing snapshots.
mysql> select removed,id,status from snapshots ;
+---------+----+------------------+
| removed | id | status |
+---------+----+------------------+
| NULL | 1 | CreatedOnPrimary |
| NULL | 2 | CreatedOnPrimary |
| NULL | 3 | BackedUp |
| NULL | 4 | Destroyed |
| NULL | 5 | BackedUp |
| NULL | 6 | BackedUp |
| NULL | 7 | Destroyed |
| NULL | 8 | BackedUp |
| NULL | 9 | Destroyed |
+---------+----+------------------+
9 rows in set (0.00 sec)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira