Troubleshoot machines creation¶
If a Machine
object is stuck in the same status for a long time,
identify the status phase of the affected machine and proceed as described
below.
To verify the status of the created Machine
objects:
kubectl --kubeconfig <pathToKindKubeconfig> \
get machines -o jsonpath='{.items[*].status.phase}'
The deployment statuses of a Machine
object are the same as the
LCMMachine
object states:
Uninitialized - the machine is not yet assigned to an
LCMCluster
.Pending - the agent reports a node IP address and host name.
Prepare - the machine executes
StateItems
that correspond to theprepare
phase. This phase usually involves downloading the necessary archives and packages.Deploy - the machine executes
StateItems
that correspond to thedeploy
phase that is becoming a Mirantis Kubernetes Engine (MKE) node.Ready - the machine is being deployed.
Upgrade - the machine is being upgraded to the new MKE version.
Reconfigure - the machine executes
StateItems
that correspond to thereconfigure
phase. The machine configuration is being updated without affecting workloads running on the machine.
If the system response is empty, approve the BootstrapRegion
object:
Using the Container Cloud web UI, navigate to the Bootstrap tab and approve the related
BootstrapRegion
objectUsing the Container Cloud CLI:
./container-cloud bootstrap approve all
If the system response is not empty and the status remains the same for a
while, the issue may relate to machine misconfiguration. Therefore, verify
and adjust the parameters of the affected Machine
object.
For provider-related issues, refer to the Troubleshooting section.