Actions
Bug #49716
closed[rbd] the "trash mv" operation should support an optional "--image-id"
Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus,octopus,pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
If the move operation was interrupted before the state could be switched from TRASh_IMAGE_STATE_MOVING to TRASH_IMAGE_STATE_NORMAL, it's not possible to recover without manually tweaking the "rbd_trash" omap values. Instead, allow the "trash mv" operation to be re-run when it gets interrupted and provide better help messages.
Updated by Jason Dillaman about 3 years ago
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
Updated by Jason Dillaman about 3 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 40010
Actually just tweaked the existing `trash_move` API to find interrupted move requests and restart them.
Updated by Mykola Golub about 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot about 3 years ago
- Copied to Backport #49766: octopus: [rbd] the "trash mv" operation should support an optional "--image-id" added
Updated by Backport Bot about 3 years ago
- Copied to Backport #49767: pacific: [rbd] the "trash mv" operation should support an optional "--image-id" added
Updated by Backport Bot about 3 years ago
- Copied to Backport #49768: nautilus: [rbd] the "trash mv" operation should support an optional "--image-id" added
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