cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Streeter (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-9744) listVirtualMachine with 'ids' field fails with invalid virtual machine id
Date Tue, 17 Jan 2017 00:29:26 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-9744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marc Streeter updated CLOUDSTACK-9744:
--------------------------------------
    Description: 
[List Virtual Machines | http://cloudstack.apache.org/api/apidocs-4.4/root_admin/listVirtualMachines.html]
offers the ability to list a batch of virtual machines by using the `ids` parameter (using
comma separated virtual machine id's).  Like so:

{code}
http://<CLOUDSTACK_HOST>/client/api?apiKey=<API_KEY>&pagesize=100&ids=835bddd8-c9d2-45ea-bf26-851a880cd142%2C5763503e-b964-4f96-bc03-2ce1cf58133b%2Cbbc739dd-e3f2-4806-94ba-dc6015e06601%2C3dcb1b2c-c370-4367-8a88-4c768b148e48%2C2738999f-c7d1-42b5-8805-41f87d648478%2C0888b622-5036-4d3c-a3d6-98d22cb4e70c%2Ccd15de56-07e7-4fd5-ad35-83d38fdd5b47&page=1&command=listVirtualMachines&signature=<SIGNATURE>&response=json&listall=true
{code}

When all `ids` provided are valid and currently-present the result provides all requested
virtual machines.  If one of the id's presented is nonexistent in the  current CloudStack
installation (whether it existed once or never existed) it results in a HTTP 431 error and
no results are returned (even  if valid id's accompany invalid id(s)).

Note -- it seems that if an invalidly formed virtual machine id is presented (i.e. one that
does not exhibit uuid formatting, such as 'foo' or 'bar') then only the  valid uuid's presented
result in rows returned.


It would be desirable that if an old/nonexistent vm id is presented in the list of other vm
ids then (whether it's a validly formatted uuid or not) it would result in rows only for valid
id's presented.  There would be no error for invalid UUID's just no corresponding row.

  was:
[List Virtual Machines | http://cloudstack.apache.org/api/apidocs-4.4/root_admin/listVirtualMachines.html]
offers the ability to list a batch of virtual machines by using the `ids` parameter (using
comma separated virtual machine id's).  Like so:

{code}
http://<CLOUDSTACK_HOST>/client/api?apiKey=<API_KEY>&pagesize=100&ids=835bddd8-c9d2-45ea-bf26-851a880cd142%2C5763503e-b964-4f96-bc03-2ce1cf58133b%2Cbbc739dd-e3f2-4806-94ba-dc6015e06601%2C3dcb1b2c-c370-4367-8a88-4c768b148e48%2C2738999f-c7d1-42b5-8805-41f87d648478%2C0888b622-5036-4d3c-a3d6-98d22cb4e70c%2Ccd15de56-07e7-4fd5-ad35-83d38fdd5b47&page=1&command=listVirtualMachines&signature=<SIGNATURE>&response=json&listall=true
{code}

When all `ids` provided are valid and currently-present uuid's the result provides all requested
virtual machines.  If one of the id's presented is nonexistent in the  current CloudStack
installation (whether it existed once or never existed) it results in a HTTP 431 error and
no results are returned (even  if valid id's accompany invalid id(s)).

Note -- it seems that if an invalidly formed virtual machine id is presented (i.e. one that
does not exhibit uuid formatting, such as 'foo' or 'bar') then only the  valid uuid's presented
result in rows returned.


It would be desirable that if an old/nonexistent vm id is presented in the list of other vm
ids then (whether it's a validly formatted uuid or not) it would result in rows only for valid
id's presented.  There would be no error for invalid UUID's just no corresponding row.


> listVirtualMachine with 'ids' field fails with invalid virtual machine id
> -------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9744
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9744
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: XenServer
>    Affects Versions: 4.4.0, 4.4.3
>            Reporter: Marc Streeter
>
> [List Virtual Machines | http://cloudstack.apache.org/api/apidocs-4.4/root_admin/listVirtualMachines.html]
offers the ability to list a batch of virtual machines by using the `ids` parameter (using
comma separated virtual machine id's).  Like so:
> {code}
> http://<CLOUDSTACK_HOST>/client/api?apiKey=<API_KEY>&pagesize=100&ids=835bddd8-c9d2-45ea-bf26-851a880cd142%2C5763503e-b964-4f96-bc03-2ce1cf58133b%2Cbbc739dd-e3f2-4806-94ba-dc6015e06601%2C3dcb1b2c-c370-4367-8a88-4c768b148e48%2C2738999f-c7d1-42b5-8805-41f87d648478%2C0888b622-5036-4d3c-a3d6-98d22cb4e70c%2Ccd15de56-07e7-4fd5-ad35-83d38fdd5b47&page=1&command=listVirtualMachines&signature=<SIGNATURE>&response=json&listall=true
> {code}
> When all `ids` provided are valid and currently-present the result provides all requested
virtual machines.  If one of the id's presented is nonexistent in the  current CloudStack
installation (whether it existed once or never existed) it results in a HTTP 431 error and
no results are returned (even  if valid id's accompany invalid id(s)).
> Note -- it seems that if an invalidly formed virtual machine id is presented (i.e. one
that does not exhibit uuid formatting, such as 'foo' or 'bar') then only the  valid uuid's
presented result in rows returned.
> It would be desirable that if an old/nonexistent vm id is presented in the list of other
vm ids then (whether it's a validly formatted uuid or not) it would result in rows only for
valid id's presented.  There would be no error for invalid UUID's just no corresponding row.



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

Mime
View raw message