github-actions[bot] commented on issue #14550: URL: https://github.com/apache/cloudstack/issues/14550#issuecomment-6580447397
> [!WARNING] > threat detection engine error > The threat detection engine encountered an error and could not complete analysis. This is a tooling failure, not a security finding. > > <!-- gh-aw-threat-engine-error --> > > <details> > <summary>What happened</summary> > > The threat detection engine failed to produce results. > > Review the [workflow run logs](https://github.com/apache/cloudstack/actions/runs/41453262605) for details. > > </details> ## ๐ฏ Triage report Since #11531 (4.22.1), Usage writes two `usage_volume` helper rows for an attached volume: a cumulative row (`vm_id` NULL) and a per-VM row. Each generates an hourly `usage_type = 6` record, and Quota bills both, so attached volumes are charged twice. The reporter describes a workaround that sets `deleted` on per-VM rows, and notes that the double charge will also reach root volumes once the unique key is widened in 4.22.2 (#13909 / #13933). ### ๐ Assessment | Dimension | Value | Reasoning | | --- | --- | --- | | **Type** | type:bug | Duplicate billing records since 4.22.1 | | **Component** | component:usage-server, component:quota | Usage writes the rows; Quota debits them | | **Severity** | Severity:Major | Account balances are debited twice for attached volumes; workaround in place | | **Labels** | type:bug, component:usage-server, component:quota, Severity:Major | | | **Coding agent** | Not suitable | Requires a decision on which record kind is billable and how existing bad records are corrected | ### ๐ Similar issues - #13909 / #13933 (related) โ unique key on `usage_volume`, referenced in the report as the reason root volumes are not yet affected - #10985 (related, closed) โ `vm_instance_id` is null for volume usage (usage\_type = 6) - #13555 (related, closed) โ volume resize usage event may record incorrect size <details> <summary>๐ก Notes and suggestions</summary> - Check the 4.22.2 plan for the unique-key change before it ships, since it would extend the double charge to root volumes. - Existing duplicate `cloud_usage` and `quota_usage` rows will need a cleanup or credit decision; the reporter removed theirs by hand. - Decide whether to bill only the cumulative record, as the reporter proposes, and check that against #11531's intent. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/41453262605) ยท copilot ยท haiku55 ยท \~2 AIC ยท โ 3.8K ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) <details> <summary><sub>Add this agentic workflow to your repo</sub></summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@139fa09ef17cde4135e696ff8e7af09bc5ddfa6e ``` </details> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, model: claude-haiku-5.5, id: 41453262605, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/41453262605 --> <!-- gh-aw-execution: {"version":1,"repo_id":"9759448","repository":"apache/cloudstack","aw_workflow_id":"daily-issue-triage","run_id":"41453262605","run_attempt":"1","run_url":"https://github.com/apache/cloudstack/actions/runs/41453262605","publishing_job":{"key":"safe_outputs","check_run_id":"125350399070"}} --> -- 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]
