[
https://issues.apache.org/jira/browse/CLOUDSTACK-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13835291#comment-13835291
]
ASF subversion and git services commented on CLOUDSTACK-4428:
-------------------------------------------------------------
Commit 37866b4a42edd38c9e6c673399249e9e1f228249 in branch refs/heads/4.2 from
[~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=37866b4 ]
CLOUDSTACK-4428: UI > volume > take snapshot action, recurring snapshot action
> for volumes whose hypervisor is KVM and whose VM is not Running, always show
the 2 actions regardless value of "kvm.snapshot.enabled".
> [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#6144)
