cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8985) Deleted volume's removed column not updated
Date Sat, 24 Oct 2015 19:38:27 GMT


ASF GitHub Bot commented on CLOUDSTACK-8985:

Github user mike-tutkowski commented on the pull request:
    I'm not at my computer right now, but I should be able to perform the
    rebase later this afternoon.
    On Saturday, October 24, 2015, Daan Hoogland <>
    > @remibergsma <> I ran the ssvm and vpc
    > tests in the env from your company and we'll have to trust Mike for the
    > solidfire specifics. He'll have to fix broken stuff there anyway. He
    > already has my lgtm
    > —
    > Reply to this email directly or view it on GitHub
    > <>.
    *Mike Tutkowski*
    *Senior CloudStack Developer, SolidFire Inc.*
    o: 303.746.7302
    Advancing the way the world uses the cloud

> Deleted volume's removed column not updated
> -------------------------------------------
>                 Key: CLOUDSTACK-8985
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.6.0
>         Environment: All
>            Reporter: Mike Tutkowski
>            Assignee: Mike Tutkowski
>             Fix For: 4.6.0
> Note: Relates to managed storage only.
> Due to the fact that a volume does not enter the "Expunged" state until after a callback
method is invoked (which happens after the plug-in is notified to delete the volume in question),
the current getUsedBytes implementation (in SolidFirePrimaryDataStoreDriver) was assuming
the volume just deleted would not be included in the used-byte count calculation.
> The fact that the code does try to count this volume in the used-byte count calculation
leads to an exception being thrown and the removed column not being updated.

This message was sent by Atlassian JIRA

View raw message