Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Orphaned snapshots remain after deleting volumes in CLVM_NG primary storage

未关闭
#14,154 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
58/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
java

调研方向

首先,在使用 CLVM_NG 的 ACS 4.23 上复现所列出的卷和快照工作流,并通过数据库和 GUI 记录跟踪卷删除路径。将其与明确的 Volume Snapshot 删除路径进行比较;完成的标准是删除原始卷后不再留下引用它的快照,同时底层的 LVM 清理仍保持完整。

由索引模型根据 Issue 内容生成。

描述

bug
problem

Issue: Orphaned snapshots remain after deleting volumes in CLVM_NG primary storage

I'm seeing an issue with CLVM_NG primary storage where snapshots persist for volumes that have already been deleted.

Reproduction steps:

  1. Deploy a VM with a single root volume that has an associated volume snapshot.
  2. Create a new volume from that snapshot.
  3. Detach the root volume from the VM.
  4. Attach the newly created volume to the VM.
  5. Delete the original volume (the one with the associated snapshot).

Observed behavior:
The snapshot remains in the system, still linked to the deleted volume.

Additional observations:

  • When deleting the volume, I can confirm that the LVM logical volumes (LVs) associated with both the root volume and its snapshot are deleted on the KVM hosts. So the underlying storage is cleaned up correctly.
  • However, the snapshot entry is not removed from the database/GUI
  • If I then manually delete the snapshot from the "Volume Snapshot" section, the operation reports success and the snapshot is no longer displayed in the GUI. This suggests the deletion works, but only when triggered explicitly against the snapshot record.

Expected behavior:
Deleting a volume should also remove (or orphan-clean) any snapshots associated with it, or at minimum the snapshot should no longer reference a non-existent volume.

versions

ACS: 4.23
Primary storage: CLVM_NG
Hypervisor: Rhel9 KVM

主要语言
Java
星标
3.1k
派生
1.4k
平均合并
6 天 20 小时
30 天内合并 PR
27

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/cloudstack 的其他 Issue

查看 apache/cloudstack 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。