If the bootstrap script fails during the deployment process, collect and inspect the bootstrap and management cluster logs.
To collect the bootstrap logs:
Log in to your local machine where the bootstrap script was executed.
Run the following command:
./bootstrap.sh collect_logs
The logs are collected in the directory where the bootstrap script is located.
Starting from the Container Cloud release 2.2.0, the logs structure
in <output_dir>/<cluster_name>/ is as follows:
/events.log - human-readable table that contains information
about the cluster events
/system - system logs
/system/<machine_name>/ucp Available since 2.3.0
- Mirantis Kuberntes Engine (MKE) logs
/objects/cluster - logs of the non-namespaced Kubernetes objects
/objects/namespaced - logs of the namespaced Kubernetes objects
/objects/namespaced/<namespaceName>/core/pods
- pods logs from a specified Kubernetes namespace
/objects/namespaced/<namespaceName>/core/pods/<containerName>.prev.log
- logs of the pods from a specified Kubernetes namespace
that were previously removed or failed
Depending on the type of issue found in logs, apply the corresponding fixes.
For example, if you detect the LoadBalancer ERROR state errors
during the bootstrap of an OpenStack-based management cluster,
contact your system administrator to fix the issue.
To troubleshoot other issues, refer to the corresponding section
in Troubleshooting.