Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set will cover all product layers, including MOSK management (formerly MCC). This means everything you need will be 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

Root cause

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

Investigation

  1. Verify the status of the MCC Exporter Pod:

    kubectl get pod -n kaas \
    -l=app.kubernetes.io/name=kaas-exporter
    
  2. 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.

  3. 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