github-actions[bot] commented on issue #12690: URL: https://github.com/apache/cloudstack/issues/12690#issuecomment-5294164890
## ๐ฏ Triage report KVM NFS primary storage is not remounted when Maintenance Mode is cancelled, leaving CloudStack reporting "Up" while the pool is physically inaccessible on the host. A maintainer (weizhouapache) has reproduced this and a second reporter confirms it on Ubuntu 24, so this is a confirmed, actionable bug affecting storage availability. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | type:bug | Clear defect: UI/DB state diverges from actual libvirt storage pool mount state | | **Component** | component:kvm, component:primary-storage | Affects KVM libvirt storage pool lifecycle for NFS primary storage | | **Severity** | Severity:Major | Storage silently inaccessible after a routine maintenance operation; workaround requires manual host intervention (restart libvirtd / pool-destroy) | | **Labels** | type:bug, component:kvm, component:primary-storage, Severity:Major | | | **Coding agent** | Not suitable | Confirmed but root cause/fix still under investigation by a maintainer; needs design decision on how CloudStack should manage pool remount on maintenance-mode exit | ### ๐ Similar issues No duplicate or closely related open issues found. <details><summary>๐ก Notes and suggestions</summary> - Maintainer weizhouapache confirmed reproduction on 2026-04-20 and stated intent to "work on a permanent fix" โ worth checking for linked PR progress. - A reported workaround is restarting `libvirtd` (no need for `virsh pool-destroy`). - Investigation should focus on `LibvirtStorageAdaptor` and how storage pool state is refreshed/reconciled when `CancelMaintenance` completes โ likely need to force a `mountpoint`/pool-refresh check and remount before marking the pool "Up". </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/31806898936) ยท sonnet50 357.5K ยท [โท](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: 31806898936, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/31806898936 --> <!-- 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]
