cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anshul1886 <...@git.apache.org>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-8413: Fixed resource tags on d...
Date Tue, 28 Apr 2015 05:12:45 GMT
GitHub user anshul1886 opened a pull request:

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

    CLOUDSTACK-8413: Fixed resource tags on disk are lost when migrate to another storage

    During cold volume migration we are duplicating volume entry in volumes table.
    When migration is complete, we update the uuid of new entry and expunge the older entry.
    This results in removal of resource tags on volume as its resource id still pointing to
older volume.
    As part of fix while updating uuid for volume, we are updating resource_id for tags also.

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

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

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

    https://github.com/apache/cloudstack/pull/194.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 #194
    
----
commit ded824bffc7900268427242a0ad357303ac5ca3b
Author: Anshul Gangwar <anshul.gangwar@citrix.com>
Date:   2015-02-19T10:52:20Z

    CLOUDSTACK-8413: Fixed resource tags on disk are lost when migrate to another storage
    
    During cold volume migration we are duplicating volume entry in volumes table.
    When migration is complete, we update the uuid of new entry and expunge the older entry.
    This results in removal of resource tags on volume as its resource id still pointing to
older volume.
    As part of fix while updating uuid for volume, we are updating resource_id for tags also.

----


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