[
https://issues.apache.org/jira/browse/CLOUDSTACK-8985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978189#comment-14978189
]
ASF subversion and git services commented on CLOUDSTACK-8985:
-------------------------------------------------------------
Commit 39c825c2c5e42a2805fb7dfcac2055d8c1edfd79 in cloudstack's branch
refs/heads/master from [~remibergsma]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=39c825c ]
Merge pull request #968 from mike-tutkowski/removed_column
CLOUDSTACK-8985: Deleted volume's removed column not updatedI found this issue
when a SolidFire integration test yesterday wasn't able to delete primary
storage because it claimed there were still volumes using the primary storage
in question (this was due to the removed column not being updated
appropriately).
I decided to go with a solution where the delete logic would pass in a volume
ID to ignore when computing the used space of the primary storage in question.
* pr/968:
CLOUDSTACK-8985: Deleted volume's removed column not updated
Signed-off-by: Remi Bergsma <git...@remi.nl>
> 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)
