[
https://issues.apache.org/jira/browse/CLOUDSTACK-7945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218737#comment-14218737
]
ASF subversion and git services commented on CLOUDSTACK-7945:
-------------------------------------------------------------
Commit 5018db8b62dbb9ddb6612914d828baf2f98c43bb in cloudstack's branch
refs/heads/4.5 from Edison Su
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5018db8 ]
CLOUDSTACK-7945:
set removed field in snapshots table in case of snaphsot failure.
Reviewed-by: Frank
> Volume Snapshots - Discrepancies in state/removed fields for Snapshots that
> are deleted
> ---------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7945
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7945
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Reporter: edison su
> Assignee: edison su
> Fix For: 4.5.0
>
>
> Currently we have 2 different ways of handing deletion of snapshot that are
> in “BackedUp” state Vs “Error” state.
> In case of Snapshots in “Error” state , we marked the removed column. But in
> case of of Snapshots in “BackedUp” state , we see that state being marked as
> “Destroyed”.
> Why is there this discrepancy?
> mysql> select id,name,status,removed from snapshots;
> --------------------------------------------------------------+
> id name status removed
> --------------------------------------------------------------+
> 1 sangee-1_ROOT-3_20141027234323 Error 2014-10-28 17:38:36
> 2 sangee-1_ROOT-3_20141027235507 Destroyed NULL
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
