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 MiraCeph custom resource (CR), which is available since MOSK 25.2 to replace the deprecated KaaSCephCluster. For the equivalent procedure with the KaaSCephCluster CR, refer to the following section:

Replace a failed Ceph OSD with a metadata device

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 the MiraCeph object as a logical volume path

• If the metadata device is specified in the MiraCeph object as a device name

Note

Ceph OSD replacement implies the usage of the CephOsdRemoveRequest custom resource (CR). For workflow overview, spec and phases description, see High-level workflow of Ceph OSD or node removal.

• Replace a failed Ceph OSD with a metadata device as a logical volume path
  • Remove a failed Ceph OSD by ID with a defined metadata device
  • Re-create a Ceph OSD with the same metadata partition
• Replace a failed Ceph OSD disk with a metadata device as a device name
  • Remove a Ceph OSD with a metadata device as a device name
  • Re-create the metadata partition on the existing metadata disk
  • Re-create the Ceph OSD with the re-created metadata partition