Volumes not destroyed after VM expunging
- 主要語言
- Java
- 星號
- 3.1k
- 分支
- 1.4k
- 平均合併
- 6 天 19 小時
- 30 天內合併 PR
- 32
描述
##### ISSUE TYPE
* Bug Report
##### COMPONENT NAME
~~~
core
~~~
##### CLOUDSTACK VERSION
~~~
4.19.0.1
~~~
##### CONFIGURATION
##### OS / ENVIRONMENT
KVM hosts (both Ubuntu 22 and OL8 as OS) with NFS v4 primary storage
Using library: libvirt 8.0.0
Using API: QEMU 8.0.0
Running hypervisor: QEMU 6.2.0
##### SUMMARY
Some volumes (only ROOT volumes) remains in Destroy state after the related VM is correctly expunged. Trying to manually delete them results in the following error: "cannot unlock file 'path-to-the-qcow2': Permission denied. Libvirtd run as root on the hosts and I found no permission/ownership issues on the qcow2 disks.
##### STEPS TO REPRODUCE
~~~
I'm not really sure on how to reproduce the issue, seems related only to root disks in our environnement, as data disks give no issues if I try to delete them.
~~~
##### EXPECTED RESULTS
~~~
When the VM is expunged also the root disk is deleted as well
~~~
##### ACTUAL RESULTS
~~~
The root disk remain in the UI in "Destroy" state
~~~
貢獻指南
研究方向
該 issue 未指出來源檔案、測試或進入點。首先追蹤所回報 KVM/NFS 環境中清除 VM 時的核心磁碟區清理流程,並調查根磁碟區為何仍處於 Destroy 狀態;完成的條件是根磁碟區會隨已清除的 VM 一起移除,且不再出現所回報的權限錯誤。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- java
- 領域
- cloud, infrastructure
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100