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.

Troubleshoot deployment stages

If the cluster deployment is stuck on the same stage for a long time, it may be related to configuration issues in the Machine or other deployment objects.

To troubleshoot cluster deployment:

1. Identify the current deployment stage that got stuck:

   kubectl --kubeconfig <pathToKindKubeconfig> \
   get cluster <cluster-name> -o jsonpath='{.status.bootstrapStatus}{"\n"}'
   

   For the deployment stages description, see Overview of the deployment workflow.

2. Collect the bootstrap-provider logs and identify a repetitive error that relates to the stuck deployment stage:

   kubectl --kubeconfig <pathToKindKubeconfig> \
   -n kaas logs -lapp.kubernetes.io/name=bootstrap-provider
   

   Examples of repetitive errors

   Error name	Solution
   Cluster nodes are not yet ready	Verify configuration of Machine objects .
   Starting pivot	Contact Mirantis support for further issue assessment.
   Some objects in cluster are not ready with the same deployment names	Verify the related deployment configuration.

See also

Collect the bootstrap logs