IBM Cloud Docs
Debugging worker nodes

Debugging worker nodes

Virtual Private Cloud Classic infrastructure

Review the options to debug your worker nodes and find the root causes for failures.

Check worker node notifications and maintenance updates

Check the IBM Cloud health and status dashboard for any notifications or maintenance updates that might be relevant to your worker nodes. These notifications or updates might help determine the cause of the worker node failures.

  1. Classic clusters Check the health dashboard for any IBM Cloud emergency maintenance notifications that might affect classic worker nodes in your account. Depending on the nature of the maintenance notification, you might need to reboot or reload your worker nodes.
  2. Check the IBM Cloud status dashboard for any known problems that might affect your worker nodes or cluster. If any of the following components show an error status, that component might be the cause of your worker node disruptions.
    • For all clusters, check the Kubernetes Service and Container Registry components.
    • For Red Hat Openshift clusters, check the Red Hat OpenShift on IBM Cloud component.
    • For VPC clusters, check the Virtual Private Cloud, Virtual Private Endpoint and Virtual Server for VPC components.
    • For Classic clusters, check the Classic Infrastructure Provisioning and Virtual Servers components.

Quick steps to resolve worker node issues

If your worker node is not functioning as expected, you can follow these steps to update your cluster and command line tools or run diagnostic tests. If the issue persists, see Debugging your worker node for additional steps.

  1. Update your cluster and worker nodes to the latest version.
  2. Update your command line tools.
  3. Run tests in the Diagnostics and Debug Tool add-on.

Debugging your worker node

Step 1: Get the worker node state

If your cluster is in a Critical, Delete failed, or Warning state, or is stuck in the Pending state for a long time, review the state of your worker nodes.

ibmcloud oc worker ls --cluster <cluster_name_or_id>

Step 2: Review the worker node state

Review the State and Status field for every worker node in your CLI output.

For more information, see Worker node states.

Step 3: Get the details for each worker node

Get the details for the worker node. If the details include an error message, review the list of common error messages for worker nodes to learn how to resolve the problem.

ibmcloud oc worker get --cluster <cluster_name_or_id> --worker <worker_node_id>

Step 4: Review the infrastructure provider for the worker node

Review the infrastructure environment to check for other reasons that might cause the worker node issues.

  1. Check with your networking team to make sure that no recent maintenance, such as firewall or subnet updates, might impact the worker node connections.
  2. Review IBM Cloud for Red Hat OpenShift on IBM Cloud and the underlying infrastructure provider, such as Virtual Servers for classic, VPC related components, or Satellite.
  3. If you have access to the underlying infrastructure, such as classic Virtual Servers, review the details of the corresponding machines for the worker nodes.