Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 59A39E484 for ; Tue, 26 Feb 2013 05:40:14 +0000 (UTC) Received: (qmail 74590 invoked by uid 500); 26 Feb 2013 05:40:13 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 74523 invoked by uid 500); 26 Feb 2013 05:40:13 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 74500 invoked by uid 99); 26 Feb 2013 05:40:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 05:40:13 +0000 Date: Tue, 26 Feb 2013 05:40:12 +0000 (UTC) From: "Sanjay Tripathi (JIRA)" To: cloudstack-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CLOUDSTACK-1374) Volume table is not getting updated with volume size. 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-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi resolved CLOUDSTACK-1374. ----------------------------------------- Resolution: Fixed > Volume table is not getting updated with volume size. > ----------------------------------------------------- > > Key: CLOUDSTACK-1374 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1374 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Affects Versions: 4.1.0 > Environment: Master branch latest code > Reporter: Sanjay Tripathi > Assignee: Sanjay Tripathi > Fix For: 4.2.0 > > > When user uploads a volume using uploadVolume API command, only volume_host_ref table is getting updated with corresponding size of volume and in "volumes" table the size of volume still remains zero even after the volumes gets completely downloaded. -- 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