[
https://issues.apache.org/jira/browse/CLOUDSTACK-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103799#comment-14103799
]
ASF subversion and git services commented on CLOUDSTACK-7337:
-------------------------------------------------------------
Commit 8d0817860faa347eb738c28d30c98f549afb3096 in cloudstack's branch
refs/heads/master from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8d08178 ]
CLOUDSTACK-7337: Volume state remains in allocated after volume creation
faliure from snapshot Volume should be marked to Destroy state after creation
faliure.
Signed-off-by: Koushik Das <[email protected]>
> Volume creation failure keeps the volume in allocated state
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-7337
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7337
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.5.0
> Reporter: Harikrishna Patnala
> Assignee: Harikrishna Patnala
> Fix For: 4.5.0
>
>
> when we try to create volume from a snapshot and upon any failure CS throws
> exception but the volume is still in Allocated state.
> This may lead to problems with the further operations when this volume (in
> allocated) is used to attach to a VM.
> We need to mark the volume to Destroy state so that no one can use that
> volume and Storage GC will clean it up later.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
