Actions
Bug #16227
closedrbd-mirror: volume rename followed by delete, not deleted on secondary
Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
I will try to reproduce this and describe the steps more exactly, but I believe a volume rename followed immediatly by a delete operaion will succeed on rename and fail to delete the volume, leaving the volume deleted correctly on the primary but remaining on the secondary.
This is triggered by deleting the parent of a cloned volume from cinder, which renames the parent until the cloned volume is deleted.
Updated by Jason Dillaman over 7 years ago
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
- Backport set to jewel
Updated by Jason Dillaman over 7 years ago
- Status changed from In Progress to Fix Under Review
- Backport deleted (
jewel)
PR: https://github.com/ceph/ceph/pull/10484
(will be backported with ticket #16538)
Updated by Mykola Golub over 7 years ago
- Status changed from Fix Under Review to Resolved
Actions