[ https://issues.apache.org/jira/browse/CLOUDSTACK-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700506#comment-13700506 ]
ASF subversion and git services commented on CLOUDSTACK-3372: ------------------------------------------------------------- Commit ac438a6d1dc21e58a6a376287147b7bcec4b327c in branch refs/heads/master from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ac438a6 ] CLOUDSTACK-3372: CapacityManager does not count destroyed volumes when deploy VMs > CapacityManager take the destroyed volume into account when caculate the > Capacity of storage pool > ------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-3372 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3372 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Reporter: Wei Zhou > Assignee: Wei Zhou > > DeployVM failed as there have not enough spaces on primary storage. > However, in fact, the primary storage have. > This is because the CapacityManager take the destroyed volume into account > when caculate the Capacity of storage pool > 2013-07-01 00:00:05,355 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-155:job-25983) We need to allocate new storagepool for this > volume > 2013-07-01 00:00:05,355 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-155:job-25983) Calling StoragePoolAllocators to find suitable > pools > 2013-07-01 00:00:05,355 DEBUG > [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-155:job-25983) > Looking for pools in dc: 1 pod:1 cluster:1 > 2013-07-01 00:00:05,356 DEBUG > [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-155:job-25983) > FirstFitStoragePoolAllocator has 1 pools to check for allocation > 2013-07-01 00:00:05,356 DEBUG > [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-155:job-25983) > Checking if storage pool is suitable, name: PRIMARY ,poolId: 200 > 2013-07-01 00:00:05,356 DEBUG > [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-155:job-25983) > Is localStorageAllocationNeeded? false > 2013-07-01 00:00:05,356 DEBUG > [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-155:job-25983) > Is storage pool shared? true > 2013-07-01 00:00:05,367 DEBUG [cloud.storage.StorageManagerImpl] > (Job-Executor-155:job-25983) Checking pool: 200 for volume allocation > [Vol[6186|vm=6068|ROOT]], maxSize : 15998461673472, totalAllocatedSize : > 13574364987392, askingSize : 64424509440, allocated disable threshold: 0.85 > 2013-07-01 00:00:05,367 DEBUG [cloud.storage.StorageManagerImpl] > (Job-Executor-155:job-25983) Insufficient un-allocated capacity on: 200 for > volume allocation: [Vol[6186|vm=6068|ROOT]] since its allocated percentage: > 0.8525063081188167 has crossed the allocated > pool.storage.allocated.capacity.disablethreshold: 0.85, skipping this pool > 2013-07-01 00:00:05,367 DEBUG > [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-155:job-25983) > FirstFitStoragePoolAllocator returning 0 suitable storage pools -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira