github-actions[bot] commented on issue #14227: URL: https://github.com/apache/cloudstack/issues/14227#issuecomment-5798922607
## ๐ฏ Triage report User reports that instance (VM) snapshots fail for some VMs with `Request failed. (530) "Failed to create Instance Snapshot: No strategy was able to handle requested snapshot for Instance ..."`, while volume snapshots work fine as a workaround. No environment details (CloudStack version, hypervisor, primary storage type) or logs were provided, so root cause can't be confirmed yet, but the error message points to the snapshot strategy selection logic (`SnapshotStrategy`) failing to find a matching strategy for the affected VM's storage/hypervisor combination. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | type:bug | Feature (instance snapshot) works for some VMs but not others โ unexpected/inconsistent failure. | | **Component** | component:primary-storage | "No strategy was able to handle requested snapshot" is raised by primary-storage snapshot strategy selection code. | | **Severity** | Severity:Minor | A workaround exists (volume snapshots) and it doesn't affect all VMs, but it does block a documented feature for a subset of instances. | | **Labels** | type:bug, component:primary-storage | See reasoning above. | | **Coding agent** | Needs more info | The bug is plausible and traceable to strategy-selection code, but without CloudStack version, hypervisor type, storage plugin, and management-server logs, an agent can't reliably reproduce or pinpoint the fix. | ### ๐ Similar issues No closely similar open issues were found in a search for this exact error message or symptom. <details><summary>๐ก Notes and suggestions</summary> To make this actionable, the reporter should be asked for: - CloudStack version (`Help > About` or `cloudstack-management` package version). - Hypervisor type/version for the affected VMs (KVM/VMware/XenServer) and whether ALL affected VMs share the same hypervisor or storage pool. - Primary storage type/plugin in use (e.g., NFS, Ceph, managed storage, local storage) for the VMs that fail vs. those that succeed โ instance snapshots typically require specific storage types (e.g., not supported on local storage or certain managed-storage plugins). - Management server log excerpt around the `530` error, including the full stack trace, to identify which `SnapshotStrategy` implementations were evaluated and why none matched. - Whether the affected VMs have any unusual configuration (e.g., mixed disk types, multiple data disks, VM snapshots already present). Likely root cause candidates: instance (VM) snapshot support is storage-plugin dependent in CloudStack (e.g., not all primary storage types support VM snapshots), so the discrepancy could be caused by affected VMs sitting on a storage pool/plugin that doesn't implement `VMSnapshotStrategy`. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/35867756133) ยท sonnet50 140.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>Add this agentic workflows to your repo</summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9 ``` </details> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-5, id: 35867756133, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/35867756133 --> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> -- 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]
