[jira] [Commented] (CLOUDSTACK-4428) [UI] "kvm.snapshot.enabled" flag should be taken to account only when snapshot is being created for Running vm

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843683#comment-13843683 ] 

ASF subversion and git services commented on CLOUDSTACK-4428:
-------------------------------------------------------------

Commit 409cbd4c7abff2a982fdced36f21e7ca5d5f5629 in branch refs/heads/4.3 from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=409cbd4 ]

CLOUDSTACK-4428: KVMsnapshoteanbled property in listCapabilities API response has been renamed. Here is corresponding UI change.


> [UI] "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.) 
>          Components: UI
>    Affects Versions: 4.2.0
>            Reporter: Alena Prokharchyk
>            Assignee: Jessica Wang
>            Priority: Critical
>             Fix For: 4.3.0
>
>         Attachments: snapshot.png
>
>
> 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 was sent by Atlassian JIRA
(v6.1.4#6159)