[
https://issues.apache.org/jira/browse/CLOUDSTACK-9668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097610#comment-16097610
]
ASF subversion and git services commented on CLOUDSTACK-9668:
-------------------------------------------------------------
Commit 970746c6d60c47a0708811c1c2533baf626d3e5b in cloudstack's branch
refs/heads/master from [~sudhansu]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=970746c ]
CLOUDSTACK-9668 : disksizeallocated of PrimaryStorage is different from the
total size of a volume
update capacity if current allocated is different from used bytes in DB.
> disksizeallocated of PrimaryStorage is different from the total size of a
> volume
> --------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9668
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.9.0
> Reporter: Sudhansu Sahu
> Assignee: Sudhansu Sahu
>
> Disksizeallocated of PrimaryStorage is different from the total size of a
> volume.
> steps to reproduce:
> 1. create another primary storage( apart from default) with storage tag (say
> tag1)
> 2. create a disk offering with storage tag as that step1.
> 3. create a data disk with above disk offering.
> 4. attach the disk to vm.
> 5. when capacity checker thread runs it will update the used_capacity. Note
> down the op_host_capacity details for pool created in step1.
> 6. detach the disk and destroy the volume.
> 7. when capacity checker thread runs it will not update the used_capacity to
> 0.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
