René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Duplicate event for VM.START in the usage_event causes it to never get processed","articleBody":"### problem\n\nIt was observed that in the usage_events table, two VM.START events for the same VM had the same timestamp\n\n| id       | type                     | account_id | created              | count | resource_id | name         |\n|----------|--------------------------|------------|----------------------|-------|-------------|--------------|\n| 106  | VM.START                 | 6        | 2025-10-27 13:02:07  | 2     | 200       | fedora  |\n| 107  | VM.STOP                  | 6        | 2025-10-27 13:02:06  | 2     | 200       | fedora  |\n| 108  | VM.START                 | 6        | 2025-10-27 13:02:07  | 2     | 200       | fedora  |\n\nThis leads to exception in createVMHelperEvent and this event is never marked as processed.\n\n```\njava.sql.SQLIntegrityConstraintViolationException: Duplicate entry '66880-1-2025-10-27 13:02:07' for key 'usage_vm_instance.vm_instance_id'\n\"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\"\n\n```\n\nThis causes the usage server to always start processing from this point.\n\n### versions\n\n_No response_\n\n### The steps to reproduce the bug\n\n1.\n2.\n3.\n...\n\n\n### What to do about it?\n\n_No response_","author":{"url":"https://github.com/abh1sar","@type":"Person","name":"abh1sar"},"datePublished":"2026-02-05T05:00:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/12590/cloudstack/issues/12590"}