abh1sar opened a new issue, #12590: URL: https://github.com/apache/cloudstack/issues/12590
### problem It was observed that in the usage_events table, two VM.START events for the same VM had the same timestamp | id | type | account_id | created | count | resource_id | name | |----------|--------------------------|------------|----------------------|-------|-------------|--------------| | 1067272 | VM.START | 653 | 2025-10-27 13:02:07 | 2 | 66880 | fedora | | 1067284 | VM.STOP | 653 | 2025-10-27 13:02:06 | 2 | 66880 | fedora | | 1067293 | VM.START | 653 | 2025-10-27 13:02:07 | 2 | 66880 | fedora | This leads to exception in createVMHelperEvent and this event is never marked as processed. ``` java.sql.SQLIntegrityConstraintViolationException: Duplicate entry '66880-1-2025-10-27 13:02:07' for key 'usage_vm_instance.vm_instance_id' "2025-12-22 00:06:57,536 ERROR [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_ba4e5a30] (Usage-Job-1:[]) (logid:) Error saving usage instance for vm: 66880 javax.persistence.EntityExistsException: Entity already exists" ``` This causes the usage server to always start processing from this point. ### versions _No response_ ### The steps to reproduce the bug 1. 2. 3. ... ### What to do about it? _No response_ -- 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]
