The ceph-exporter pods are present in the Ceph crash list¶
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 unsupported
KaaSCephCluster resource. And MiraCeph will be automatically migrated
to CephDeployment in MOSK 26.1. For details, see Deprecation Notes:
KaaSCephCluster API on management clusters.
For the equivalent procedure with the unsupported KaaSCephCluster 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.