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 Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.
The ceph-exporter pods are present in the Ceph crash list¶
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:
After a MOSK cluster update, the ceph-exporter pods may
be present in the ceph crash ls or ceph health detail
list while rook-ceph-exporter attempts to obtain the port that is still in
use. For example:
ceph health detail
HEALTH_WARN 1 daemons have recently crashed
[WRN] RECENT_CRASH: 1 daemons have recently crashed
client.ceph-exporter crashed on host kaas-node-b59f5e63-2bfd-43aa-bc80-42116d71188c at 2024-10-01T16:43:31.311563Z
The issue does not block the MOSK cluster update. Once the
port becomes available, rook-ceph-exporter obtains the port and the issue
disappears.
To apply the issue resolution, run ceph crash archive-all to
remove ceph-exporter pods from the Ceph crash list.