Bug 1942515 - rook-ceph-osd-X gets stuck in initcontainer expand-encrypted-bluefs
Summary: rook-ceph-osd-X gets stuck in initcontainer expand-encrypted-bluefs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: rook
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: OCS 4.6.4
Assignee: Sébastien Han
QA Contact: Elad
URL:
Whiteboard:
Depends On: 1941977
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-24 13:38 UTC by Mudit Agarwal
Modified: 2021-06-01 08:47 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Earlier, when running encrypted OSDs on multipath, the expand container failed to find the underlying device of the encrypted block. This was due to the underlying block was located in /dev/mapper and this path was not mounted in the init container "expand-encrypted-bluefs".
Clone Of: 1941977
Environment:
Last Closed: 2021-04-08 10:29:01 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:1134 0 None None None 2021-04-08 10:29:13 UTC

Comment 13 errata-xmlrpc 2021-04-08 10:29:01 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 (Red Hat OpenShift Container Storage 4.6.4 container bug fix update), 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-2021:1134
Note You need to log in before you can comment on or make changes to this bug.