[
https://issues.apache.org/jira/browse/CLOUDSTACK-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070580#comment-15070580
]
ASF GitHub Bot commented on CLOUDSTACK-9200:
--------------------------------------------
Github user anshul1886 commented on the pull request:
https://github.com/apache/cloudstack/pull/1282#issuecomment-167040721
@pdube Snapshot can be in Allocated state for a split second only in normal
scenarios. If it is in Allocated state for more than that time, then it simply
means we are either restarting or have to restart the management server. Now if
that's the case then it should have been cleaned up by storage cleanup thread
during management server start if it has job associated with it. But that is
not happening so it is falling in this scenario.
> 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.4#6332)
