cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From likitha <...@git.apache.org>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-8609. [VMware] VM is not acces...
Date Thu, 02 Jul 2015 10:29:15 GMT
GitHub user likitha opened a pull request:

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

    CLOUDSTACK-8609. [VMware] VM is not accessible after a migration acro…

    …ss clusters.
    
    Once a VM is successfully started, don't delete the files associated with the unregistered
VM, if the files are in a storage that is being used by the new VM.
    Attempt to unregister a VM in another DC, only if there is a host associated with a VM.

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

    $ git pull https://github.com/likitha/cloudstack CLOUDSTACK-8609

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

    https://github.com/apache/cloudstack/pull/556.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 #556
    
----
commit a97a402f304303af78552777d5fde56abab902e5
Author: Likitha Shetty <likitha.shetty@citrix.com>
Date:   2015-05-15T08:44:37Z

    CLOUDSTACK-8609. [VMware] VM is not accessible after a migration across clusters.
    Once a VM is successfully started, don't delete the files associated with the unregistered
VM, if the files are in a storage that is being used by the new VM.
    Attempt to unregister a VM in another DC, only if there is a host associated with a VM.

----


---
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