Actions
Bug #42405
closed[rbd-mirror] v2 clone non-primary snapshot can leave snapshot in trash
% Done:
0%
Source:
Community (user)
Tags:
Backport:
nautilus,mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Description
> 1. create snapshot of primary image > 2. wait for the snapshot to appear on the backup cluster > 3. create a clone in backup cluster (using Simplified RBD Image Cloning - no snap protect) > 4. delete the snapshot of the primary image - this is to save space because the clone will last a long time> 5. if I do rbd --cluster backup snap ls --all IMAGENAME it presents the deleted snapshot in the namespace trash > 6. delete the clone > 7. I expected that deleting the clone would purge the snapshot from trash, but it doesn't > 8. trash purge or trash remove is impossible (read only filesystem)
Updated by Mykola Golub over 4 years ago
- Status changed from New to In Progress
- Assignee set to Mykola Golub
Updated by Mykola Golub over 4 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 31260
Updated by Jason Dillaman over 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42699: nautilus: [rbd-mirror] v2 clone non-primary snapshot can leave snapshot in trash added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42700: mimic: [rbd-mirror] v2 clone non-primary snapshot can leave snapshot in trash added
Updated by Nathan Cutler about 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions