[
https://issues.apache.org/jira/browse/CLOUDSTACK-9417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15338552#comment-15338552
]
ASF GitHub Bot commented on CLOUDSTACK-9417:
--------------------------------------------
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1593
@jburwell If no sanity-check-last-id is present it will run Sanity on the
whole cloud_usage data set and then create a new sanity-check-last-id file. The
whole part of sanity checking related to sanity-check-last-id has been broken
for a while since the part to update sanity-check-last-id wasn't in the code.
> Usage module refactoring
> ------------------------
>
> Key: CLOUDSTACK-9417
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9417
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Usage
> Affects Versions: 4.9.0
> Reporter: Nicolas Vazquez
> Assignee: Nicolas Vazquez
> Fix For: 4.9.0
>
>
> h3. Introduction
> Usage sanity check file was not been updated on sanity check.
> It is proposed:
> * New usage folder {{/var/cache/cloudstack/usage}}, creation on
> cloudstack-usage package built.
> * New sanity check file location in new folder {{/var/cache/cloudstack/usage}}
> * Timestamp included in {{usage.log}} file
> * Include {{updateMaxId()}} on sanity check as it wasn't being updated
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
