Project

General

Profile

Actions

Bug #41206

closed

failed to remove image with mirroring enabled and data pool deleted

Added by Mykola Golub almost 5 years ago. Updated over 4 years ago.

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

0%

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

Description

Steps to reproduce:
- create a mirroring image with data pool
- delete data pool
- try to remove image

It fails with the error:

2019-08-12T11:23:00.568+0100 7f1f93fff700 -1 librbd::image::RemoveRequest: 0x7f1f84002200 handle_mirror_image_remove: failed to remove mirror image state: (16) Device or resource busy
2019-08-12T11:23:00.600+0100 7f1fc7d66f40 -1 librbd::api::Trash: enable_mirroring: failed to retrieve features: (2) No such file or directory
Removing image: 0% complete...failed.

It is because the image open step fails due deleted data pool, and RemoveRequest skips many steps, one of them is disabling mirroring, and later it fails when trying to remove the image entry from rbd_mirror object.

As we do not have any guard to forbid data pool deletion if it is still in use, it would be nice to make `rbd remove` robust enough not to fail in such case.


Related issues 1 (0 open1 closed)

Copied to rbd - Backport #41629: nautilus: failed to remove image with mirroring enabled and data pool deletedResolvedJason DillamanActions
Actions #1

Updated by Mykola Golub almost 5 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 29613
Actions #2

Updated by Jason Dillaman over 4 years ago

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

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41629: nautilus: failed to remove image with mirroring enabled and data pool deleted added
Actions #4

Updated by Jason Dillaman over 4 years ago

  • Status changed from Pending Backport to Resolved
Actions #5

Updated by Jason Dillaman over 4 years ago

  • Status changed from Resolved to Pending Backport
Actions #6

Updated by Jason Dillaman over 4 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF