You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Prasanna Santhanam (JIRA)" <ji...@apache.org> on 2013/02/01 07:01:18 UTC
[jira] [Resolved] (CLOUDSTACK-1123) ListStoragePools API broken by
refactor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasanna Santhanam resolved CLOUDSTACK-1123.
--------------------------------------------
Resolution: Fixed
Fixed in master, commit 6a6d93c3094a55c38f2bdcc736d179ce1e595093
> ListStoragePools API broken by refactor
> ---------------------------------------
>
> Key: CLOUDSTACK-1123
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1123
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: API
> Affects Versions: 4.1.0
> Reporter: Prasanna Santhanam
> Assignee: Min Chen
> Labels: integration-test
> Fix For: 4.1.0
>
>
> From: Devdeep Singh <de...@citrix.com>
> To: "cloudstack-dev@incubator.apache.org"
> <cl...@incubator.apache.org>
> Date: Thu, 31 Jan 2013 21:43:47 +0530
> I observed that the lisStoragePools api is broken if it is called with a parameter. E.g if called with the zoneid parameter it fails with the following exception
> ERROR [cloud.api.ApiServer] (ApiServer-4:) unhandled exception executing api command: listStoragePools
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@3f135a: SELECT DISTINCT(storage_pool_view.id) FROM storage_pool_view WHERE storage_pool_view.cluster_id = ** STREAM DATA ** AND storage_pool_view.removed IS NULL ORDER BY storage_pool_view.id ASC LIMIT 0, 500
> at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:410)
> at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
> at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:345)
--
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