cinder-backup ceph snapshot delete
Bug #1933265 reported by
masterpe
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Low
|
Unassigned |
Bug Description
When we create a backup in Openstack using version Train and Ussuri with a Ceph based volume and backup.
Ceph is running Nautilus.
When we create 4 backups of a volume that volume gets 4 snapshots on the source. When we delete all of the backups the 4 backups still exists on the source volume.
To reproduce we do:
openstack volume create --size 1 vol1
This volume gets ID: 4dad898a-
then 4 times: openstack volume backup create 4dad898a-
At the Ceph cluster we see at rbd info -p volumes volume-
snapshot_count: 4
Changed in cinder: | |
importance: | Undecided → Low |
tags: | added: backup-service ceph rbd snapshot |
To post a comment you must log in.
Yes, I have been wondering about this myself.
Apparently there was a major change in snapshot management to the cinder-backup ceph driver:
https:/ /github. com/openstack/ cinder/ commit/ bc9ab142da91908 7c71525978f9601 15ff0259b9 /bugs.launchpad .net/cinder/ +bug/1703011
Bug: https:/
This causes all snapshots created on the source volume of a backup to remain (see https:/ /github. com/openstack/ cinder/ commit/ bc9ab142da91908 7c71525978f9601 15ff0259b9# diff-ad4253afa3 19b756b36939988 0a46ef8b186e46d beb6ee06896c243 f1f349e6fL716) together with "their" backups. Only if backups are deleted both the snapshots (target as well as source) should be cleaned up.
also see the discussion at https:/ /bugs.launchpad .net/cinder/ +bug/1907542
There is a discussion around volumes and their (user hidden) relation to the snapshots they originated from and how to resolve this transparently for the user while maintaining the storage efficiency.
* https:/ /bugs.launchpad .net/cinder/ +bug/1677525 /review. opendev. org/c/openstack /cinder/ +/754397
* https:/