Bug 1561758 - Failed to delete RBD image with error - "cannot obtain exclusive lock - not removing" and no watchers in rbd status
Summary: Failed to delete RBD image with error - "cannot obtain exclusive lock - not r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RBD-Mirror
Version: 3.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: z1
: 3.1
Assignee: Jason Dillaman
QA Contact: Vasishta
Bara Ancincova
URL:
Whiteboard:
Depends On:
Blocks: 1584264
TreeView+ depends on / blocked
 
Reported: 2018-03-28 20:14 UTC by Vikhyat Umrao
Modified: 2021-06-10 15:34 UTC (History)
8 users (show)

Doc Type: Bug Fix
Doc Text:
.RBD images can now be removed even if the optional journal is missing or corrupt If the RBD journaling feature is enabled, a missing journal prevents the image from being opened in an attempt to prevent possible data corruption. This safety feature also prevented an image from being removed if its journal was unavailable. Previously, the journaling feature had to be disabled before attempting to remove the image if this situation occurred. With this update, RBD image removal skips any attempt to open the journal because its integrity is not important when the image is being deleted. As a result, RBD images can now be removed even if the optional journal is missing or corrupt.
Clone Of:
Environment:
Last Closed: 2018-11-09 00:59:17 UTC

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 23512 0 None None None 2018-03-29 15:44:58 UTC
Red Hat Product Errata RHBA-2018:3530 0 None None None 2018-11-09 01:00:30 UTC

Description Vikhyat Umrao 2018-03-28 20:14:59 UTC 
Description of problem:
Failed to delete RBD image with error - "cannot obtain exclusive lock - not removing Removing image: 0% complete...failed. rbd: error: image still has watchers" and no watchers in rbd status command.

Version-Release number of selected component (if applicable):
Red Hat Ceph Storage 3


How reproducible:
Always at the customer site.
Comment 19 errata-xmlrpc 2018-11-09 00:59:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3530
Note You need to log in before you can comment on or make changes to this bug.