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 8AF451062A for ; Fri, 3 Jan 2014 05:20:15 +0000 (UTC) Received: (qmail 78405 invoked by uid 500); 3 Jan 2014 05:20:07 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 78324 invoked by uid 500); 3 Jan 2014 05:20:03 -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 78167 invoked by uid 500); 3 Jan 2014 05:19:58 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 78140 invoked by uid 99); 3 Jan 2014 05:19:56 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jan 2014 05:19:56 +0000 Date: Fri, 3 Jan 2014 05:19:56 +0000 (UTC) From: "prashant kumar mishra (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-5742) #cpu,cpu speed, and ram is getting updated under wrong usage_type(2) for dynamic compute offering in usage_vm_instance table MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 prashant kumar mishra created CLOUDSTACK-5742: ------------------------------------------------- Summary: #cpu,cpu speed, and ram is getting updated under wrong usage_type(2) for dynamic compute offering in usage_vm_instance table Key: CLOUDSTACK-5742 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5742 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: prashant kumar mishra Priority: Critical Fix For: 4.3.0 STEPS TO REPO ============== 1-prepare a CS setup 4.3 2-deploy a vm with small CO 3-Change the vm CO to dynamic CO. 4-check the usage_vm_instance table after cloud_usage db synch EXPECTED ========= cpu and ram should get updated under usage type 1 ACTUAL ======= cpu and ram is getting updated under usage type2 DB === | 2 | 1 | 2 | 8 | test | 12 | 202 | XenServer | 2014-01-03 10:10:15 | NULL | 100 | 1 | 256 | | 1 | 1 | 2 | 8 | test | 12 | 202 | XenServer | 2014-01-03 10:11:21 | NULL | NULL | NULL | NULL | +------------+---------+------------+----------------+---------+---------------------+-------------+-----------------+---------------------+---------------------+-----------+-----------+--------+ -- This message was sent by Atlassian JIRA (v6.1.5#6160)