Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A04C8C972 for ; Mon, 9 Sep 2013 10:38:56 +0000 (UTC) Received: (qmail 75727 invoked by uid 500); 9 Sep 2013 10:38:56 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 75573 invoked by uid 500); 9 Sep 2013 10:38:55 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 75548 invoked by uid 500); 9 Sep 2013 10:38:54 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 75538 invoked by uid 99); 9 Sep 2013 10:38:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Sep 2013 10:38:51 +0000 Date: Mon, 9 Sep 2013 10:38:51 +0000 (UTC) From: "Indra Pramana (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-3542) Ceph RBD provides wrong usage info to CloudStack MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761751#comment-13761751 ] Indra Pramana commented on CLOUDSTACK-3542: ------------------------------------------- Hi Frederik, I am now using libvirt 1.1.1, but the problem was resolved when I installed 1.1.0. I believe 1.1.2 should also resolve the problem. root@hv-kvm-01:/home/indra# virsh --version 1.1.1 What QEMU/KVM version you are using? May want to try upgrading QEMU as well, although not too sure whether it'll help to resolve the problem. I am using QEMU version 1.5.1 but on qemu.org website, version 1.5.3 and 1.6.0 are already out. root@hv-kvm-01:/home/indra# kvm --version QEMU emulator version 1.5.1, Copyright (c) 2003-2008 Fabrice Bellard > Ceph RBD provides wrong usage info to CloudStack > ------------------------------------------------ > > Key: CLOUDSTACK-3542 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3542 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Doc > Affects Versions: 4.1.0 > Environment: Ubuntu 12.04.2 > Reporter: Indra Pramana > Assignee: sadhu suresh > Labels: ceph, doc, rbd > > I am installing CloudStack 4.1.0 to use Ceph RBD as primary storage. I failed to create VM instance using the RBD as primary storage because Ceph provides wrong disk usage information. See below: > root@hv-kvm-02:~# virsh pool-info bab81ce8-d53f-3a7d-b8f6-841702f65c89 > Name: bab81ce8-d53f-3a7d-b8f6-841702f65c89 > UUID: bab81ce8-d53f-3a7d-b8f6-841702f65c89 > State: running > Persistent: no > Autostart: no > Capacity: 5.47 TiB > Allocation: 34819.02 TiB <-- wrong information > Available: 5.47 TiB > Record on the "storage_pool" table on "cloud" database: > +-----+-----------------+--------------------------------------+-------------------+------+----------------+--------+------------+-------------------+----------------+---------------------------+------------------------------------------------+------------------------+---------------------+---------------------+-------------+-------------+---------------------+-------+ > | id | name | uuid | pool_type | port | data_center_id | pod_id | cluster_id | available_bytes | capacity_bytes | host_address | user_info | path | created | removed | update_time | status | storage_provider_id | scope | > +-----+-----------------+--------------------------------------+-------------------+------+----------------+--------+------------+-------------------+----------------+---------------------------+------------------------------------------------+------------------------+---------------------+---------------------+-------------+-------------+---------------------+-------+ > | 209 | sc-image | bab81ce8-d53f-3a7d-b8f6-841702f65c89 | RBD | 6789 | 6 | 6 | 6 | 38283921137336466 | 6013522722816 | ceph-mon.xxx.com | admin:xxx | sc1 | 2013-07-13 08:58:27 | NULL | NULL | Up | NULL | NULL | > === > 2013-07-15 11:27:31,632 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) System Alert: Low Available Storage in cluster Cluster-01 pod Pod-01 of availability zone 01 > 2013-07-15 11:27:31,632 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Available storage space is low, total: 13282342 MB, used: 36510398411 MB (274879.22%) > === > As a result, VM instance creation fails since it's not able to find available storage pool. > === > 2013-07-15 11:15:28,313 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-3:job-168) Checking pool: 208 for volume allocation [Vol[227|vm=225|ROOT]], maxSize : 15828044742656, totalAllocatedSize : 1769538048, askingSize : 8589934592, allocated disable threshold: 0.85 > 2013-07-15 11:15:28,313 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) Checking if storage pool is suitable, name: sc-image ,poolId: 209 > 2013-07-15 11:15:28,313 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) Is localStorageAllocationNeeded? false > 2013-07-15 11:15:28,313 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) Is storage pool shared? true > 2013-07-15 11:15:28,317 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-3:job-168) Checking pool 209 for storage, totalSize: 6013522722816, usedBytes: 38283921137336466, usedPct: 6366.305226067051, disable threshold: 0.85 > 2013-07-15 11:15:28,317 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-3:job-168) Insufficient space on pool: 209 since its usage percentage: 6366.305226067051 has crossed the pool.storage.capacity.disablethreshold: 0.85 > 2013-07-15 11:15:28,317 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-3:job-168) FirstFitStoragePoolAllocator returning 1 suitable storage pools > 2013-07-15 11:15:28,317 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-3:job-168) Checking suitable pools for volume (Id, Type): (228,DATADISK) > 2013-07-15 11:15:28,317 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-3:job-168) We need to allocate new storagepool for this volume > 2013-07-15 11:15:28,319 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-3:job-168) Calling StoragePoolAllocators to find suitable pools > 2013-07-15 11:15:28,319 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-3:job-168) Looking for pools in dc: 6 pod:6 cluster:6 having tags:[rbd] > 2013-07-15 11:15:28,322 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-3:job-168) FirstFitStoragePoolAllocator has 1 pools to check for allocation > 2013-07-15 11:15:28,322 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) Checking if storage pool is suitable, name: sc-image ,poolId: 209 > 2013-07-15 11:15:28,322 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) Is localStorageAllocationNeeded? false > 2013-07-15 11:15:28,322 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) Is storage pool shared? true > 2013-07-15 11:15:28,326 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-3:job-168) Checking pool 209 for storage, totalSize: 6013522722816, usedBytes: 38283921137336466, usedPct: 6366.305226067051, disable threshold: 0.85 > 2013-07-15 11:15:28,326 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-3:job-168) Insufficient space on pool: 209 since its usage percentage: 6366.305226067051 has crossed the pool.storage.capacity.disablethreshold: 0.85 > 2013-07-15 11:15:28,326 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-3:job-168) FirstFitStoragePoolAllocator returning 0 suitable storage pools > 2013-07-15 11:15:28,326 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-3:job-168) No suitable pools found for volume: Vol[228|vm=225|DATADISK] under cluster: 6 > 2013-07-15 11:15:28,326 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-3:job-168) No suitable pools found > 2013-07-15 11:15:28,326 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-3:job-168) No suitable storagePools found under this Cluster: 6 > 2013-07-15 11:15:28,326 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-3:job-168) Could not find suitable Deployment Destination for this VM under any clusters, returning. > 2013-07-15 11:15:28,332 DEBUG [cloud.vm.UserVmManagerImpl] (Job-Executor-3:job-168) Destroying vm VM[User|Indra-Test-3] as it failed to create on Host with Id:null > 2013-07-15 11:15:28,498 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-3:job-168) VM state transitted from :Stopped to Error with event: OperationFailedToErrorvm's original host id: null new host id: null host id before state transition: null > 2013-07-15 11:15:29,125 INFO [user.vm.DeployVMCmd] (Job-Executor-3:job-168) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|Indra-Test-3]Scope=interface com.cloud.dc.DataCenter; id=6 > === -- 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