[
https://issues.apache.org/jira/browse/JCLOUDS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734133#comment-13734133
]
Andrew Bayer commented on JCLOUDS-240:
--------------------------------------
If you have sufficient logging enabled, you should be able to see the GET call
in jclouds-wire.log (or whatever file your logs are going to) that's actually
doing the listUsageRecords - any chance you could find that and verify that
it's got the right start/end date strings there? If so, then, well, we've got a
CloudStack bug here. =)
> listUsageRecords API for CloudStack: Start Date and End Date not taken into
> account properly
> --------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-240
> URL: https://issues.apache.org/jira/browse/JCLOUDS-240
> Project: jclouds
> Issue Type: Bug
> Affects Versions: 1.7.0, 1.6.1
> Reporter: edo
>
> Provided a start and end date to listUsageRecords (i.e. 2013-08-05 and
> 2013-08-06). However, the usage records contains dates outside that timeframe
> specified.
> The interface used was: org.jclouds.cloudstack.features.GlobalUsageApi
> listUsageRecords
--
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
