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.

Troubleshoot Mirantis Container Cloud Exporter alerts¶

This section describes the investigation and troubleshooting steps for the Mirantis Container Cloud Exporter (MCC Exporter) service alerts.

MCCExporterTargetDown
MCCUpdateBlocked

MCCExporterTargetDown¶

Root cause	Prometheus failed to scrape MCC Exporter metrics because of the `kaas-exporter` Pod outage or application error.
Investigation	Verify the status of the MCC Exporter Pod: kubectl get pod -n kaas \ -l=app.kubernetes.io/name=kaas-exporter Inspect the Kubernetes Pod events, if available: kubectl describe pod -n kaas <pod_name> Alternatively: In the Discover section of OpenSearch Dashboards, change the index pattern to kubernetes_events-. Expand the required time range and filter the results by kubernetes.event.involved_object.name that equals the `<pod_name>`. In results, search for kubernetes.event.message. Inspect MCC Exporter logs for error or warning messages: kubectl logs -n kaas <pod_name> For further steps, see the Investigation* section of the KubePodsCrashLooping alert.
Mitigation	Refer to KubePodsCrashLooping.

Root cause

Prometheus failed to scrape MCC Exporter metrics because of the kaas-exporter Pod outage or application error.

Investigation

Verify the status of the MCC Exporter Pod:

kubectl get pod -n kaas \
-l=app.kubernetes.io/name=kaas-exporter

Inspect the Kubernetes Pod events, if available:
```
kubectl describe pod -n kaas <pod_name>
```
Alternatively:
1. In the Discover section of OpenSearch Dashboards, change the index pattern to kubernetes_events-*.
2. Expand the required time range and filter the results by kubernetes.event.involved_object.name that equals the <pod_name>.
3. In results, search for kubernetes.event.message.
Inspect MCC Exporter logs for error or warning messages:
```
kubectl logs -n kaas <pod_name>
```

For further steps, see the Investigation section of the KubePodsCrashLooping alert.

Mitigation

Refer to KubePodsCrashLooping.

MCCUpdateBlocked¶

Root cause	The Container Cloud update may be blocked due to one of the following reasons: One or more unsupported managed clusters that must be updated to a supported Cluster release One or more unsupported regional clusters that must be removed Cluster update is in progress
Investigation and mitigation	Verify that the Cluster versions of your managed clusters are supported by the target Container Cloud release. For details, see Cluster versions compatibility. To update a MOSK cluster, see Cluster update. Verify that Container Cloud does not include any regional clusters. If this is the case, remove them as described in Remove a management cluster. On the Clusters page of the Container Cloud web UI, verify that no clusters are in the Updating` status. Otherwise, wait until the update is complete.

Root cause

The Container Cloud update may be blocked due to one of the following reasons:

One or more unsupported managed clusters that must be updated to a supported Cluster release
One or more unsupported regional clusters that must be removed
Cluster update is in progress

Investigation and mitigation

Verify that the Cluster versions of your managed clusters are supported by the target Container Cloud release. For details, see Cluster versions compatibility.

To update a MOSK cluster, see Cluster update.
Verify that Container Cloud does not include any regional clusters. If this is the case, remove them as described in Remove a management cluster.
On the Clusters page of the Container Cloud web UI, verify that no clusters are in the Updating` status. Otherwise, wait until the update is complete.