Project

General

Profile

Bug #16227

rbd-mirror: volume rename followed by delete, not deleted on secondary

Added by Jon Bernard over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Target version:
-
Start date:
06/10/2016
Due date:
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

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.

History

#1 Updated by Jason Dillaman over 2 years ago

  • Status changed from New to In Progress
  • Assignee set to Jason Dillaman
  • Backport set to jewel

#2 Updated by Jason Dillaman over 2 years ago

  • Status changed from In Progress to Need Review
  • Backport deleted (jewel)

PR: https://github.com/ceph/ceph/pull/10484

(will be backported with ticket #16538)

#3 Updated by Mykola Golub over 2 years ago

  • Status changed from Need Review to Resolved

Also available in: Atom PDF