Bug 1495979 - daemon: only call close_encrypted_part on dmcrypt
Summary: daemon: only call close_encrypted_part on dmcrypt
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Container
Version: 3.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: 3.0
Assignee: Sébastien Han
QA Contact: Vasishta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-26 13:33 UTC by Sébastien Han
Modified: 2022-02-21 18:19 UTC (History)
7 users (show)

Fixed In Version: rhceph:ceph-3.0-rhel-7-docker-candidate-72190-20170926144216
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-05 23:19:04 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-docker pull 793 0 None None None 2017-09-26 13:34:02 UTC
Red Hat Product Errata RHEA-2017:3388 0 normal SHIPPED_LIVE new container image: rhceph-3-rhel7 2017-12-06 02:43:29 UTC

Description Sébastien Han 2017-09-26 13:33:03 UTC 
Description of problem:

while preparing a device we call close_encrypted_part which breaks the container and results in the following output during prepare:

Device 635e0cbc-5b37-49f0-8159-8a8fdf65d648 is not active.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 5 Vasishta 2017-10-24 06:39:26 UTC 
It was able for me to prepare OSDs (filestore) both colocated and dedicated journals with and without dmcrypt using ceph-3.0-rhel-7-docker-candidate-24891-20171020102128, moving BZ to VERIFIED state.
Comment 8 errata-xmlrpc 2017-12-05 23:19:04 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/RHEA-2017:3388
Note You need to log in before you can comment on or make changes to this bug.