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

Cloudstack allows you to create snapshots with the same name for the same volume

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

还没有人认领这个 Issue。

评估

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

调研方向

首先,在一个卷上为两个具有相同名称的快照重现所列步骤,然后跟踪涉及的快照创建和删除路径。完成的标准是 CloudStack 拒绝重复项,或者在删除其中一个快照时,保持快照条目和 secondary-storage 文件的一致性。

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

描述

component:primary-storage type:bug
problem

Bug report:
CloudStack allows creating multiple snapshots of the same volume with identical names.

Image These snapshots are treated as separate entities in CloudStack, but they reference the same snapshot file on secondary storage. Image

The snapshot file on secondary storage is overwritten when a snapshot with the same name is created
Image

When one of these snapshots is deleted via CloudStack. The snapshot file is removed from secondary storage. Other snapshot entries remain in CloudStack but no longer have a corresponding file.

Deleted a snapshot in Cloudstack
Image
The first snapshot was deleted from CloudStack. During the deletion process, CloudStack also removed the snapshot file from secondary storage.

Image

However, a second snapshot entry still remains in the database and references a file on secondary storage that no longer exists.

Image
versions

ACS: 4.20.2.0
Hypervisor: KVM
Primary Storage: Linstor
Secondary Storage: NFS

The steps to reproduce the bug
  1. Create a volume
  2. Create snapshot with name for example "test-snapshot"
  3. Create another snapshot with the same name "test-snapshot"
  4. Verify that both snapshots exist in CloudStack and only one exists on the secondary storage
  5. Delete ONE of the snapshots via CloudStack
  6. Check secondary storage — snapshot file is removed
  7. Check remaining snapshot in CloudStack
What to do about it?

Prevent creating snapshots with the same name for the same volume. Deleting one breaks the other.

主要语言
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 摘要。