[
https://issues.apache.org/jira/browse/CLOUDSTACK-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747303#comment-13747303
]
ASF subversion and git services commented on CLOUDSTACK-4428:
-------------------------------------------------------------
Commit 5d90c60d63a9b8801f27973f33accc4f8f8168fc in branch refs/heads/4.2 from
[~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5d90c60 ]
CLOUDSTACK-4428: "kvm.snapshot.enabled" flag shouldn't affect detached volumes,
or volumes attached to the vm in Stopped/Destroyed state
(cherry picked from commit 97cb0093c82b1032ccc4ecad838d4c65c3bf99d2)
Signed-off-by: animesh <anim...@apache.org>
> "kvm.snapshot.enabled" flag should be taken to account only when snapshot is
> being created for Running vm
> ---------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4428
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4428
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Reporter: Alena Prokharchyk
> Assignee: Alena Prokharchyk
> Priority: Critical
> Fix For: 4.2.1
>
>
> We used to have a problem for KVM snapshot creation when createSnapshot is
> called for the volume of the Running vm. As a fix for that,
> kvm.snapshot.enabled flag was introduced. But when this flag set to fase, it
> doesn't allow snapshot creation even for detached volumes (the area where the
> problem didn't even exist).
> Suggested fix: kvm.snapshot.enabled should affect only case when the snapshot
> is being created for the volume a) that is attached to the vm b) the vm is
> running/starting/stopping states only
--
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
