Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1496528

Summary:	daemon: do not run umount lockbox
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Sébastien Han <shan>
Component:	Container	Assignee:	Sébastien Han <shan>
Status:	CLOSED ERRATA	QA Contact:	Vasishta <vashastr>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.0	CC:	anharris, dang, hchen, jim.curtis, kdreyer, pprakash, vashastr
Target Milestone:	rc
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhceph:ceph-3.0-rhel-7-docker-candidate-24159-20170927165426	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-05 23:19:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sébastien Han 2017-09-27 16:51:53 UTC

Description of problem:

Even if it runs with || true and won't fail this is really confusing for
users.

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-16 13:41:31 UTC

It was possible to bring up dmcrypt osds (filestore, colocated and dedicated journal) using ceph-3.0-rhel-7-docker-candidate-96603-20171012221250.

Moving BZ to VERIFIED state, Please let me know if there are any concerns.

Regards,
Vasishta

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