[
https://issues.apache.org/jira/browse/CLOUDSTACK-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15581670#comment-15581670
]
Rohit Yadav commented on CLOUDSTACK-9474:
-----------------------------------------
Looks like this duplicates:
https://issues.apache.org/jira/browse/CLOUDSTACK-8896
> When attaching a pool to an instance the askingSize parameter of pool checker
> is 0
> ----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9474
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9474
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.9.0
> Environment: * VMware vCenter 5.5U3/ESXi 5.0 U1
> * ACS 4.9 running on CentOS6.4
> Reporter: Boris Stoyanov
>
> *Description:*
> When attaching a pool to an instance the askingSize parameter of pool checker
> is 0. Which basically makes a ineffective check of the storage pool
> *Setup:*
> 1 VMware cluster with 2 Hosts.
> *Executed Steps:*
> # Applied the following global settings:
> #* storage.overprovisioning.factor = 1
> #* pool.storage.allocated.capacity.disablethreshold = 1
> #* pool.storage.capacity.disablethreshold = 1
> # Restarted management server
> # Created a storage pool in ready state
> # Attach the pool to a running instance
> *Result:*
> In the logs found that the actual parameter of askingSize is 0, when
> attaching a pool to an instance.
> {code}
> 2016-08-19 08:50:06,606 DEBUG [c.c.s.StorageManagerImpl]
> (Work-Job-Executor-32:ctx-d1de6fb2 job-421/job-422 ctx-05433821)
> (logid:7a659fd1) Checking pool: 203 for volume allocation
> [Vol[118|vm=null|DATADISK]], maxSize : 4292870144000, totalAllocatedSize :
> 8590663680, askingSize : 0, allocated disable threshold: 1.0{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
