Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!
Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly MCC). This means everything you need is in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.
Replace a failed Ceph OSD with a metadata device¶
Warning
This procedure is valid for MOSK clusters that use the deprecated
KaaSCephCluster
custom resource (CR) instead of the MiraCeph
CR that is
available since MOSK 25.2 as a new Ceph configuration entrypoint. For the
equivalent procedure with the MiraCeph
CR, refer to the following section:
The document describes various scenarios of a Ceph OSD outage and recovery or replacement. More specifically, this section describes how to replace a failed Ceph OSD with a metadata device:
If the metadata device is specified as a logical volume in the
BareMetalHostProfile
object and defined in theKaaSCephCluster
object as a logical volume pathIf the metadata device is specified in the
KaaSCephCluster
object as a device name
Note
Ceph OSD replacement implies the usage of the
KaaSCephOperationRequest
custom resource (CR). For workflow overview,
spec and phases description, see High-level workflow of Ceph OSD or node removal.