[
https://issues.apache.org/jira/browse/CLOUDSTACK-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958436#comment-15958436
]
ASF GitHub Bot commented on CLOUDSTACK-9200:
--------------------------------------------
Github user rhtyd commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1282#discussion_r110092478
--- Diff:
engine/storage/snapshot/src/org/apache/cloudstack/storage/snapshot/XenserverSnapshotStrategy.java
---
@@ -245,6 +245,12 @@ public boolean deleteSnapshot(Long snapshotId) {
return true;
}
+ if(snapshotVO.getState() == Snapshot.State.Allocated) {
--- End diff --
@anshul1886 the code to check and remove snapshot when they are stuck in
Allocated state is already in line 223 above, in the same method. Why this
redundancy, is this a synchronization issue?
> Account Resources fail to get cleaned up if a snapshot is in Allocated State
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9200
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9200
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Anshul Gangwar
> Assignee: Anshul Gangwar
>
> If a snapshot ( Volume ) is in Allocated state (snapshots table), and if we
> delete the account associated with that account, it is removed from UI but
> the account resources (snapshots and virtual machines) are not cleaned up
> because of the failure to delete the snapshot which is in Allocated state.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
