cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From koushik-das <...@git.apache.org>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-8655: [Browser Based Upload Vo...
Date Tue, 21 Jul 2015 09:12:03 GMT
GitHub user koushik-das opened a pull request:

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

    CLOUDSTACK-8655: [Browser Based Upload Volume] Partially uploaded vol…

    …umes are not getting destroyed as part of storage GC
    
    As part of volume sync, that runs during of SSVM start-up, the volume_store_ref entry
was getting deleted. Volume GC relies on this entry to move volume to destroyed state.
    Since the entry was getting deleted, GC thread never moved the volume from UploadError/UploadAbandoned
to Destroyed. Fix is to not remove the volume_store_ref entry as part
    of volume sync and let GC thread handle the clean up.

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

    $ git pull https://github.com/koushik-das/cloudstack CLOUDSTACK-8655

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

    https://github.com/apache/cloudstack/pull/611.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 #611
    
----
commit b3e0099e0a0ea9b22a350320f56a8421823fedc1
Author: Koushik Das <koushik@apache.org>
Date:   2015-07-21T08:58:38Z

    CLOUDSTACK-8655: [Browser Based Upload Volume] Partially uploaded volumes are not getting
destroyed as part of storage GC
    As part of volume sync, that runs during of SSVM start-up, the volume_store_ref entry
was getting deleted. Volume GC relies on this entry to move volume to destroyed state.
    Since the entry was getting deleted, GC thread never moved the volume from UploadError/UploadAbandoned
to Destroyed. Fix is to not remove the volume_store_ref entry as part
    of volume sync and let GC thread handle the clean up.

----


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