[
https://issues.apache.org/jira/browse/CLOUDSTACK-8985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972810#comment-14972810
]
ASF GitHub Bot commented on CLOUDSTACK-8985:
--------------------------------------------
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/968#issuecomment-150840869
@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
> Deleted volume's removed column not updated
> -------------------------------------------
>
> Key: CLOUDSTACK-8985
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8985
> 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
(v6.3.4#6332)
