StepBee commented on issue #6717: URL: https://github.com/apache/cloudstack/issues/6717#issuecomment-1887890519
For the moment, i see for all affected volumes one field in the database is NULL, which is not the case for not affected volumes. Affected volumes: ``` cloud_usage.usage_volume.deleted = NULL ``` for not affected volumes: ``` cloud_usage.usage_volume.deleted = <date-of-deletion> ``` Following your question to the issue from 2018 and following the usage aggregation logic, for both types of volumes i see two events in the database table "cloud.usage_event" - one entry with type "VOLUME.CREATE" - one entry with type "VOLUME.DELETE" The entries in the "cloud.usage_event" table are as expected - and the same applies to the copy in cloud_usage.usage_event table. So it looks like something (sometimes) is missing the VOLUME.DELETE event during the first aggregation to the helper table "cloud_usage.usage_volume" -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
