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 0C34410493 for ; Fri, 6 Dec 2013 22:49:37 +0000 (UTC) Received: (qmail 51768 invoked by uid 500); 6 Dec 2013 22:49:36 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 51753 invoked by uid 500); 6 Dec 2013 22:49:36 -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 51745 invoked by uid 500); 6 Dec 2013 22:49:36 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 51735 invoked by uid 99); 6 Dec 2013 22:49:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 22:49:36 +0000 Date: Fri, 6 Dec 2013 22:49:36 +0000 (UTC) From: "Prachi Damle (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CLOUDSTACK-5343) Volume limit applied to project/account does not count root disks 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-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle resolved CLOUDSTACK-5343. -------------------------------------- Resolution: Cannot Reproduce > Volume limit applied to project/account does not count root disks > ----------------------------------------------------------------- > > Key: CLOUDSTACK-5343 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5343 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Storage Controller > Affects Versions: 4.3.0 > Reporter: Gaurav Aradhye > Assignee: Prachi Damle > Fix For: 4.3.0 > > > 1. Create any project or account. > 2. Set the volume limit as 1. > 3. Deploy an instance without data disk in project/account. > 4. Now you can see the root disk in the volumes, but if you list the account/project, then the volume count still shows as 0. > 5. Now add new data disk. > 6. Check volume count, now it shows it as 1 (But it should have shown as 2, and it should have failed at this stage only saying limit exceeded.) > 7. Add another data disk (Now it will fail) -- This message was sent by Atlassian JIRA (v6.1#6144)