Project

General

Profile

Actions

Bug #51021

closed

"trash purge" shouldn't stop at the first unremovable image

Added by Ilya Dryomov almost 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus,octopus,pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

As there is no inherent ordering, there may be multiple removable images past the unremovable image. In addition, removing a clone image may make its parent image removable.

Ensure that a single "trash purge" call cleans up as much as possible. A repeated "trash purge" call with nothing in between should be a no-op.


Related issues 3 (0 open3 closed)

Copied to rbd - Backport #51057: nautilus: "trash purge" shouldn't stop at the first unremovable imageResolvedIlya DryomovActions
Copied to rbd - Backport #51058: pacific: "trash purge" shouldn't stop at the first unremovable imageResolvedIlya DryomovActions
Copied to rbd - Backport #51059: octopus: "trash purge" shouldn't stop at the first unremovable imageResolvedIlya DryomovActions
Actions #1

Updated by Ilya Dryomov almost 3 years ago

  • Pull request ID set to 41588
Actions #2

Updated by Ilya Dryomov almost 3 years ago

  • Status changed from In Progress to Fix Under Review
  • Backport set to nautilus,octopus,pacific
Actions #3

Updated by Ilya Dryomov almost 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Backport Bot almost 3 years ago

  • Copied to Backport #51057: nautilus: "trash purge" shouldn't stop at the first unremovable image added
Actions #5

Updated by Backport Bot almost 3 years ago

  • Copied to Backport #51058: pacific: "trash purge" shouldn't stop at the first unremovable image added
Actions #6

Updated by Backport Bot almost 3 years ago

  • Copied to Backport #51059: octopus: "trash purge" shouldn't stop at the first unremovable image added
Actions #7

Updated by Loïc Dachary almost 3 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

Also available in: Atom PDF