github-actions[bot] commented on issue #13771: URL: https://github.com/apache/cloudstack/issues/13771#issuecomment-5356777304
## ๐ฏ Triage report When importing an existing shared/local KVM disk via `importVm importsource=shared|local`, the ROOT volume is always assigned `deviceid=1` instead of `0`, regardless of storage backend (RBD, Linstor, qcow2/NFS). The VM still boots and functions correctly, but this is inconsistent with the external/VMware and staged import paths (which correctly import ROOT with `deviceId=null`, defaulting to 0) and can confuse any code or user relying on ROOT = device 0. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | type:bug | Clear, reproducible deviceId assignment inconsistency traced to a specific code path | | **Component** | component:kvm, component:managed-storage | Affects `UnmanagedVMsManagerImpl`'s KVM shared/local disk import (`importKVMSharedDisk`/`importKVMLocalDisk`) | | **Severity** | Severity:Minor | Cosmetic/data-consistency issue โ VM boots and operates normally; only `listVolumes` output and assumptions about ROOT=device 0 are affected | | **Labels** | type:bug, component:kvm, component:managed-storage, Severity:Minor | See above | | **Coding agent** | Suitable | Root cause is precisely identified (a stray `deviceId = 1L` intended for post-ROOT data disks was applied to ROOT itself), the fix is a one-line change (pass `null`/`0` for ROOT, matching the existing VMware/staged import pattern), and a maintainer has already confirmed no pushback on the approach | ### ๐ Similar issues No closely related open duplicates found. <details><summary>๐ก Notes and suggestions</summary> Maintainer nvazquez confirmed the fix approach (deviceId=null for ROOT, consistent with the external import path) should be safe for single-volume VMs. This is a small, well-isolated, low-risk change โ a good candidate for a quick PR. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/32375697891) ยท sonnet50 224.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: 32375697891, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/32375697891 --> <!-- 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]
