You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Marc Brashear (JIRA)" <ji...@apache.org> on 2013/07/08 10:33:48 UTC
[jira] [Commented] (CLOUDSTACK-1297) listVirtualMachines api does
not return for the instance name of the Vm created
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701876#comment-13701876 ]
Marc Brashear commented on CLOUDSTACK-1297:
-------------------------------------------
I am seeing this bug in for XenServer in CloudStack 4.1 as well. If listVirtualMachines is run via the API I receive all VM instances. If I specify the name of an instance in the query, I get no results:
http://x.x.x.x:8080/client/api?command=listVirtualMachines&name=VLAB02-WOPT-DEMO
<listvirtualmachinesresponse cloud-stack-version="4.1.0"/>
List with no filter:
http://x.x.x.x:8080/client/api?command=listVirtualMachines
<listvirtualmachinesresponse cloud-stack-version="4.1.0">
<count>1</count>
<virtualmachine>
<id>b92e02b2-f800-46a5-8e62-380b4577d1f9</id>
<name>VLAB02-WOPT-DEMO</name>
<displayname>VLAB02-DEMO-WOPT-1</displayname>
<account>admin</account>
<domainid>deba188c-e228-11e2-9c07-566ad45d4d5b</domainid>
<domain>ROOT</domain>
<created>2013-07-08T01:41:18+0000</created>
<state>Running</state>
<haenable>false</haenable>
<zoneid>f708ed1a-d010-4b97-96e1-6f6d8a36f14e</zoneid>
<zonename>VLAB02-ZONE-1</zonename>
<hostid>9f168376-3a5f-426a-850c-9f58831b935e</hostid>
<hostname>VLAB02-HOST-1</hostname>
<templateid>9d96af1f-5a1b-4dee-a54b-39a282091731</templateid>
<templatename>VLAB02-WOPT</templatename>
<templatedisplaytext>VLAB02-WOPT</templatedisplaytext>
<passwordenabled>false</passwordenabled>
<serviceofferingid>a89c0aee-3dd4-4e1d-ad4d-eacf1ca4ccd2</serviceofferingid>
<serviceofferingname>WOPT</serviceofferingname>
<cpunumber>1</cpunumber>
<cpuspeed>1000</cpuspeed>
<memory>2048</memory>
<cpuused>2.11%</cpuused>
<networkkbsread>201</networkkbsread>
<networkkbswrite>191</networkkbswrite>
<guestosid>df812026-e228-11e2-9c07-566ad45d4d5b</guestosid>
<rootdeviceid>0</rootdeviceid>
<rootdevicetype>ROOT</rootdevicetype>
<nic>
<id>afed50ed-4030-4e4f-8cf0-e94d8b8a6498</id>
<networkid>35552563-bd95-4c97-a591-d614ce594033</networkid>
<networkname>WOPT-WAN-400</networkname>
<netmask>255.255.255.248</netmask>
<gateway>1.1.1.1</gateway>
<ipaddress>1.1.1.2</ipaddress>
<isolationuri>vlan://400</isolationuri>
<broadcasturi>vlan://400</broadcasturi>
<traffictype>Guest</traffictype>
<type>Shared</type>
<isdefault>true</isdefault>
<macaddress>06:97:2c:00:00:88</macaddress>
</nic>
<nic>
<id>9dd29926-231a-4c09-8a79-20519ddfb498</id>
<networkid>ed792a27-0bdd-4087-9f93-bf65c13427da</networkid>
<networkname>WOPT-LAN-400</networkname>
<netmask>255.255.255.248</netmask>
<gateway>2.2.2.1</gateway>
<ipaddress>2.2.2.2</ipaddress>
<isolationuri>vlan://400</isolationuri>
<broadcasturi>vlan://400</broadcasturi>
<traffictype>Guest</traffictype>
<type>Shared</type>
<isdefault>false</isdefault>
<macaddress>06:49:e2:00:00:83</macaddress>
</nic>
<nic>
<id>9cf14057-5b43-4b9c-9ebd-004bce008edf</id>
<networkid>5ab86f1b-bceb-4feb-9ca5-b73a5839c617</networkid>
<networkname>VM-MGMT-30</networkname>
<netmask>255.255.255.0</netmask>
<gateway>56.0.4.1</gateway>
<ipaddress>56.0.4.21</ipaddress>
<isolationuri>vlan://30</isolationuri>
<broadcasturi>vlan://30</broadcasturi>
<traffictype>Guest</traffictype>
<type>Shared</type>
<isdefault>false</isdefault>
<macaddress>06:50:3c:00:00:15</macaddress>
</nic>
<hypervisor>XenServer</hypervisor>
<instancename>i-2-26-VM</instancename>
<tags>
<key>name</key>
<value>VLAB02-DEMO-WOPT-1</value>
<resourcetype>UserVm</resourcetype>
<resourceid>b92e02b2-f800-46a5-8e62-380b4577d1f9</resourceid>
<account>admin</account>
<domainid>deba188c-e228-11e2-9c07-566ad45d4d5b</domainid>
<domain>ROOT</domain>
</tags>
<tags>
<key>name</key>
<value>VLAB02-DEMO-WOPT-1</value>
<resourcetype>UserVm</resourcetype>
<resourceid>b92e02b2-f800-46a5-8e62-380b4577d1f9</resourceid>
<account>admin</account>
<domainid>deba188c-e228-11e2-9c07-566ad45d4d5b</domainid>
<domain>ROOT</domain>
</tags>
<tags>
<key>name</key>
<value>VLAB02-DEMO-WOPT-1</value>
<resourcetype>UserVm</resourcetype>
<resourceid>b92e02b2-f800-46a5-8e62-380b4577d1f9</resourceid>
<account>admin</account>
<domainid>deba188c-e228-11e2-9c07-566ad45d4d5b</domainid>
<domain>ROOT</domain>
</tags>
</virtualmachine>
</listvirtualmachinesresponse>
> listVirtualMachines api does not return for the instance name of the Vm created
> -------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1297
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1297
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: irfan
>
> I have deployed CloudStack 3.0.2 on ESXi Vm in vCenter.
> listVirtualMachines api does not return for the instance name of the Vm created
--
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