github-actions[bot] commented on issue #14645: URL: https://github.com/apache/cloudstack/issues/14645#issuecomment-6802609812
> [!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/43029422543) for details. > > </details> ## 🎯 Triage report A size-only `resizeVolume` of a running system VM's volume succeeds, but the running VM never sees the new size. `orchestrateResizeVolume` looks the VM up only as a user VM, so for a system VM it sends the resize with no instance and skips the hypervisor checks. On KVM the image grows, but `virsh blockresize` is never run for the domain. The reporter proposes refusing the resize unless the system VM is stopped, which keeps the current stopped-VM behaviour. ### 📊 Assessment | Dimension | Value | Reasoning | | --- | --- | --- | | **Type** | type:bug | API reports success while the running VM is out of step with its volume | | **Component** | component:kvm | Reproduced on KVM; the resize path is in `VolumeApiServiceImpl` | | **Severity** | Severity:Minor | Guest sees the new size after restart; no data loss reported | | **Labels** | type:bug, component:kvm, Severity:Minor | | | **Coding agent** | Suitable | The proposed change (refuse unless stopped) is small and specific | ### 🔗 Similar issues - #14601 (related) — ROOT volume grow through a disk offering is refused while running; the other side of the same running-VM resize rules - #14622 (related) — RBD resize fails until libvirt refreshes the pool <details> <summary>💡 Notes and suggestions</summary> - Reproduction: resize the ROOT volume of a running virtual router, then compare `virsh domblkinfo` and `lsblk` in the router. - A maintainer should confirm refusing, rather than a live resize, is the intended behaviour. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/43029422543) · copilot · haiku55 · \~6 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: 43029422543, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/43029422543 --> <!-- gh-aw-execution: {"version":1,"repo_id":"9759448","repository":"apache/cloudstack","aw_workflow_id":"daily-issue-triage","run_id":"43029422543","run_attempt":"1","run_url":"https://github.com/apache/cloudstack/actions/runs/43029422543","publishing_job":{"key":"safe_outputs","check_run_id":"130687254582"}} --> -- 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]
