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

ASF GitHub Bot commented on CLOUDSTACK-8663:
--------------------------------------------

GitHub user anshul1886 opened a pull request:

    https://github.com/apache/cloudstack/pull/1941

    CLOUDSTACK-8663: Fixed various issues to allow VM snapshots and volume

    snapshots to exist together
    
    Reverting VM to disk only snapshot in Xenserver corrupts VM
    
    Stale NFS secondary storage on XS leads to volume creation failure from 
snapshot
    
    Fixed various concerns raised in #672 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-8663

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1941.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1941
    
----
commit ca84fd4ffd5d80aef9c7624365d29d7b2aeb3225
Author: Anshul Gangwar <[email protected]>
Date:   2015-07-24T09:15:20Z

    CLOUDSTACK-8663: Fixed various issues to allow VM snapshots and volume
    snapshots to exist together
    
    Reverting VM to disk only snapshot in Xenserver corrupts VM
    
    Stale NFS secondary storage on XS leads to volume creation failure from 
snapshot

----


> Snapshot Improvements
> ---------------------
>
>                 Key: CLOUDSTACK-8663
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8663
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
>             Fix For: Future
>
>
> Split volume snapshot process
> Allow VM snapshot and volume snapshots to exist together



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to