Bug 1756371 - Should not fail when trying to remove crypt mapper
Summary: Should not fail when trying to remove crypt mapper
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Volume
Version: 4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 4.0
Assignee: Christina Meno
QA Contact: Vasishta
URL:
Whiteboard:
Depends On:
Blocks: 1729267 1733577 1738236
TreeView+ depends on / blocked
 
Reported: 2019-09-27 13:30 UTC by Mike Hackett
Modified: 2020-01-31 12:47 UTC (History)
4 users (show)

Fixed In Version: ceph-14.2.4-5.el8cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-31 12:47:11 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph pull 30490 0 'None' closed ceph-volume: do not fail when trying to remove crypt mapper 2020-02-04 09:30:27 UTC
Red Hat Product Errata RHBA-2020:0312 0 None None None 2020-01-31 12:47:31 UTC

Description Mike Hackett 2019-09-27 13:30:46 UTC
Description of problem:
In a containerized context, at some point, need to run simple scan on a device
from a separate container (not the existing and running corresponding container
to that device), but this can't work because when it tries to remove the
mapper which is still in use by the corresponding running osd container,
it fails.
This can be a bit more permissive and simply throw a warning.

Closes: https://tracker.ceph.com/issues/41392

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

Version-Release number of selected component (if applicable):
4.0

Comment 8 errata-xmlrpc 2020-01-31 12:47:11 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-2020:0312


Note You need to log in before you can comment on or make changes to this bug.