Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 7 Aug 2013 18:46:19 +0000 (UTC)
From: "Animesh Chaturvedi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12653834.1371692007739.18215.1375901179438@arcas>
In-Reply-To: <JIRA.12653834.1371692007739@arcas>
References: <JIRA.12653834.1371692007739@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-3080) listVirtualMachines tag search
 refinement no longer working
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Animesh Chaturvedi updated CLOUDSTACK-3080:
-------------------------------------------


These blockers and critical issues are resolved but not verified. Reporters of these issues please verify the fixes and help close these issues
                
> listVirtualMachines tag search refinement no longer working
> -----------------------------------------------------------
>
>                 Key: CLOUDSTACK-3080
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3080
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.1.0, 4.2.0
>            Reporter: Nick Wales
>            Assignee: Min Chen
>            Priority: Critical
>              Labels: api, listvirtualmachines
>             Fix For: 4.1.1, 4.2.0
>
>
> In 4.0.1 I was able to make a call to the API similar to the below which would return only the instances tagged as eg (app=my_app_name).
> { :command=>"listVirtualMachines",
> "tags[0].value"=>"my_app_name",
>  "tags[0].key"=>"app"}
> (I'm using the cloudstack_helper ruby gem which explains the formatting)
> However since I have upgraded to 4.1 I now get returned every instance for the same query.

--
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