Return-Path: <issues-return-77347-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 16967200BDB
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon, 12 Dec 2016 12:25:00 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 1525D160B22; Mon, 12 Dec 2016 11:25:00 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 602E7160B0D
	for <archive-asf-public@cust-asf.ponee.io>; Mon, 12 Dec 2016 12:24:59 +0100 (CET)
Received: (qmail 29387 invoked by uid 500); 12 Dec 2016 11:24:58 -0000
Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:issues@cloudstack.apache.org>
List-Id: <issues.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list issues@cloudstack.apache.org
Received: (qmail 29378 invoked by uid 500); 12 Dec 2016 11:24:58 -0000
Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org
Received: (qmail 29375 invoked by uid 99); 12 Dec 2016 11:24:58 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Dec 2016 11:24:58 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 561362C03DD
	for <cloudstack-issues@incubator.apache.org>; Mon, 12 Dec 2016 11:24:58 +0000 (UTC)
Date: Mon, 12 Dec 2016 11:24:58 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12864207.1442313152000.497271.1481541898349@Atlassian.JIRA>
In-Reply-To: <JIRA.12864207.1442313152000@Atlassian.JIRA>
References: <JIRA.12864207.1442313152000@Atlassian.JIRA> <JIRA.12864207.1442313152432@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8857)  'listProjects' doesn't return
 tags 'vmstopped' or 'vmrunning' when their value is zero
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Mon, 12 Dec 2016 11:25:00 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8857?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D15741670#comment-15741670 ]=20

ASF GitHub Bot commented on CLOUDSTACK-8857:
--------------------------------------------

Github user blueorangutan commented on the issue:

    https://github.com/apache/cloudstack/pull/838
 =20
    Packaging result: =E2=9C=94centos6 =E2=9C=94centos7 =E2=9C=94debian. JI=
D-391


>  'listProjects' doesn't return tags 'vmstopped' or 'vmrunning' when their=
 value is zero
> -------------------------------------------------------------------------=
--------------
>
>                 Key: CLOUDSTACK-8857
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-885=
7
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>            Reporter: Bharat Kumar
>            Assignee: Bharat Kumar
>
>  'listProjects' doesn't return tags 'vmstopped' or 'vmrunning' when their=
 value is zero.
> Eg:
> API result when 1 vm is stopped and 0 vms are running:
> curl -s 'http://127.0.0.1:8096/api?command=3DlistProjects&account=3Dadmin=
&domainid=3D10513804-76ec-11e4-924f-065db2000097' 2>/dev/null | xmllint --f=
ormat - -o=20
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>=20
> <listprojectsresponse cloud-stack-version=3D"4.3.0.1">=20
> <count>1</count>=20
> <project>=20
> <id>a811d7e1-3ec7-4dda-92c4-4792200f38cf</id>=20
> <name>abc</name>=20
> <displaytext>abc</displaytext>=20
> <domainid>10513804-76ec-11e4-924f-065db2000097</domainid>=20
> <domain>ROOT</domain>=20
> <account>admin</account>=20
> <state>Active</state>=20
> <networklimit>20</networklimit>=20
> <networktotal>1</networktotal>=20
> <networkavailable>19</networkavailable>=20
> <vpclimit>20</vpclimit>=20
> <vpctotal>0</vpctotal>=20
> <vpcavailable>20</vpcavailable>=20
> <cpulimit>40</cpulimit>=20
> <cputotal>1</cputotal>=20
> <cpuavailable>39</cpuavailable>=20
> <memorylimit>40960</memorylimit>=20
> <memorytotal>512</memorytotal>=20
> <memoryavailable>40448</memoryavailable>=20
> <primarystoragelimit>200</primarystoragelimit>=20
> <primarystoragetotal>2</primarystoragetotal>=20
> <primarystorageavailable>198</primarystorageavailable>=20
> <secondarystoragelimit>400</secondarystoragelimit>=20
> <secondarystoragetotal>0</secondarystoragetotal>=20
> <secondarystorageavailable>400</secondarystorageavailable>=20
> <vmlimit>20</vmlimit>=20
> <vmtotal>1</vmtotal>=20
> <vmavailable>19</vmavailable>=20
> <iplimit>20</iplimit>=20
> <iptotal>1</iptotal>=20
> <ipavailable>4</ipavailable>=20
> <volumelimit>20</volumelimit>=20
> <volumetotal>1</volumetotal>=20
> <volumeavailable>19</volumeavailable>=20
> <snapshotlimit>20</snapshotlimit>=20
> <snapshottotal>0</snapshottotal>=20
> <snapshotavailable>20</snapshotavailable>=20
> <templatelimit>20</templatelimit>=20
> <templatetotal>1</templatetotal>=20
> <templateavailable>19</templateavailable>=20
> <vmstopped>1</vmstopped>=20
> </project>=20
> </listprojectsresponse>
> The above response should have a tag <vmrunning>0</vmrunning>, which is m=
issing, similar when the zero vms are stopped, vmstopped would be missing. =
When there are no VMs in the project neither of these tags are in the respo=
nse.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)