cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sateesh-chodapuneedi <...@git.apache.org>
Subject [GitHub] cloudstack pull request #1828: CLOUDSTACK-9676 Start instance fails after re...
Date Wed, 14 Dec 2016 09:09:52 GMT
GitHub user sateesh-chodapuneedi opened a pull request:

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

    CLOUDSTACK-9676 Start instance fails after reverting to a VM snapshot when there are child
VM snapshots

    Jira
    ===
    CLOUDSTACK-9676 Start instance fails after reverting to a VM snapshot when there are child
VM snapshots
    
    Issue
    ====
    Start instance fails after reverting to a VM snapshot, when there is 1 or more child VM
snapshots in the snapshot tree of the VM.
    Per the code that detects the presence of a snapshot, we are checking for only current
snapshot instead of checking presence of any snapshot in the snapshot tree.
    The failure to detect all snapshots means ACP reconfigures the VM in wrong way assuming
there are no snapshots for the VM.
    This results in start failure.
    
    Fix
    ===
    Ensure correct detection of VM snapshots in the VM snapshot tree
    


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

    $ git pull https://github.com/sateesh-chodapuneedi/cloudstack pr-cloudstack-9676

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

    https://github.com/apache/cloudstack/pull/1828.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 #1828
    
----
commit 34c85f5847dd4d3e55700e324bf695c60b8a4ca6
Author: Sateesh Chodapuneedi <sateesh.chodapuneedi@accelerite.com>
Date:   2016-12-13T20:22:15Z

    CLOUDSTACK-9676 Start instance fails after reverting to a VM snapshot, when there are
child VM snapshots
    
    Issue
    ====
    Start instance fails after reverting to a VM snapshot, when there is 1 or more child VM
snapshots in the snapshot tree of the VM.
    Per the code that detects the presence of a snapshot, we are checking for only current
snapshot instead of checking presence of any snapshot in the snapshot tree.
    The failure to detect all snapshots means ACP reconfigures the VM in wrong way assuming
there are no snapshots for the VM.
    This results in start failure.
    
    Fix
    ===
    Ensure correct detection of VM snapshots in the VM snapshot tree
    
    Signed-off-by: Sateesh Chodapuneedi <sateesh.chodapuneedi@accelerite.com>

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message