René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[cloud_usage] vm_instance_id is null for volume usage (usage_type = 6)","articleBody":"### problem\n\nWhen tracking volume usage in the `cloud_usage` table` (usage_type = 6)`, the `vm_instance_id` field is `NULL`, even if the volume is currently attached to a VM. This leads to potential inaccuracies in historical usage data, especially when volumes are detached and reattached to different VMs.\n\nExpected Behavior: ACS should record the correct `vm_instance_id` associated with a volume when usage occurs and store it in the `cloud_usage` table.\n\n### versions\n\nThe ACS version is 4.19.1.1\n\n### The steps to reproduce the bug\n\nCase 1:\n\n1. Create and attach a volume to VM.\n2. Use the VM for some time (allow usage data to be generated).\n3. Observe that cloud_usage.vm_instance_id is still NULL for this VM.\n\nCase 2:\n\n1. Create and attach a volume to VM A.\n2. Use the VM for some time (allow usage data to be generated).\n3. Detach the volume and attach it to VM B.\n4. Trigger a reprocessing of usage data for the original time period.\n5. Observe that cloud_usage.vm_instance_id is still NULL.\n\n### What to do about it?\n\nConsider enhancing the ACS `UsageManagerImpl` or submitting a patch upstream to ensure `vm_instance_id` is consistently captured and stored when usage is recorded.\n\nMy goal is to accurately track historical usage of volumes in relation to the VMs they were attached to. To achieve this and mitigate the issue of missing `vm_instance_id` values for` usage_type =` 6 in the `cloud_usage` table.","author":{"url":"https://github.com/Yuliia7-1","@type":"Person","name":"Yuliia7-1"},"datePublished":"2025-06-06T19:01:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/10985/cloudstack/issues/10985"}