[ https://issues.apache.org/jira/browse/CLOUDSTACK-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561915#comment-13561915 ]
Min Chen commented on CLOUDSTACK-355: ------------------------------------- listCapacity command relies on some in-memory stats, so cannot be fixed through DB view approach. > Fix "count" in a bunch of API commands > -------------------------------------- > > Key: CLOUDSTACK-355 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-355 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server > Affects Versions: 4.1.0 > Reporter: Alena Prokharchyk > Assignee: Min Chen > Fix For: 4.1.0 > > > Count should be fixed for following list commands (as a part of Search Engine > refactoring) > listResourceLimits > listIsos > listTemplates > listLoadBalancerRuleInstances > listCapacity > listHosts > listSecurityGroups > listNetworks > listVPCs > listTemplatePermissions > listIsoPermissions > listServiceOfferings > listDiskOfferings > listNetworkDevice > listVPCOfferings > listTrafficTypeImplementors > listSnapshotPolicies > listLBStickinessPolicies > listCapabilities > listZones > listEventTypes > listSwifts > listHypervisors > listNetworkOfferings > listSupportedNetworkServices > listStorageNetworkIpRange > listEvents -- 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