Newer documentation is now live.You are currently reading an older version.

Troubleshoot machine 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 the prepare phase. This phase usually involves downloading the necessary archives and packages.

  • Deploy - the machine executes StateItems that correspond to the deploy phase that is becoming a Mirantis Kubernetes Engine (MKE) node.

  • Ready - all StateItems of the machine are set and successfully processed by the agent.

  • Reconfigure - the machine executes StateItems that correspond to the reconfigure phase. The machine configuration is being updated without affecting workloads running on the machine.

  • Upgrade - the machine is being updated to match the desired configuration, for example, to a new MKE version.

  • Reboot - the machine is being rebooted to complete the changes applied during the Reconfigure or Upgrade state. On a management cluster, the machine is rebooted automatically. On a MOSK cluster, the operator triggers the reboot by creating a GracefulRebootRequest object.

Note

A machine that has reached the Ready state can return to the Reconfigure, Upgrade, or Reboot state when the corresponding changes are requested. After the changes are processed, the machine returns to the Ready state.

If the system response is empty, approve the BootstrapRegion object using the MOSK management 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.