Help Center/ Cloud Container Engine/ FAQs/ Workload/ Workload Exception Troubleshooting/ How Can I Locate the Root Cause If a Workload Is Abnormal?
Updated on 2025-07-17 GMT+08:00

How Can I Locate the Root Cause If a Workload Is Abnormal?

If a workload is abnormal, you can check the pod events first to locate the fault and then rectify the fault.

Fault Locating

To locate the fault of an abnormal workload, take the following steps:

  1. Check whether the workload pod is running properly.

    1. Log in to the CCE console.
    2. Click the cluster name to access the cluster console. In the navigation pane, choose Workloads.
    3. In the upper left corner of the page, select the namespace, locate the target workload, and view its status.
      • If the workload is not ready, you can view pod events to determine the cause. For details, see Viewing Pod Events. You can find the solution to the issue based on the events by referring to Common Pod Issues.
      • If the workload is processing, wait patiently.
      • If the workload is running, but it is not accessible, check whether intra-cluster access is normal.

  2. Check whether access within the cluster is normal.

    Log in to the CCE console or use kubectl to obtain the pod IP address. Then, log in to the node or the pod and run curl or use other methods to manually call the APIs and check whether the intra-cluster communication is normal.

    If {Container IP address}:{Port number} is not accessible, log in to the service container, and attempt to access 127.0.0.1:{Port number}.

    For details about how to log in to a container, see Logging In to a Container.

  3. Check whether the expected results are displayed.

    If the workload is accessible within the cluster but the expected results are not shown, check the workload configurations, such as verifying if the image tag and environment variables are correctly configured.

Common Pod Issues

Status

Description

Reference

Pending

The pod scheduling failed.

What Should I Do If the Scheduling of a Pod Fails?

Pending

A storage volume fails to be mounted to a pod.

What Should I Do If a Storage Volume Cannot Be Mounted or the Mounting Times Out?

Pending

The storage volume mounting failed.

What Should I Do If a Workload Exception Occurs Due to a Storage Volume Mount Failure?

FailedPullImage

ImagePullBackOff

The image pull failed.

The image failed to be pulled again.

What Should I Do If a Pod Fails to Pull the Image?

CreateContainerError

CrashLoopBackOff

The container startup failed.

The container failed to restart.

What Should I Do If a Pod Startup Fails?

Evicted

A pod is in the Evicted state, and the pod keeps being evicted.

What Should I Do If a Pod Fails to Be Evicted?

Creating

A pod is in the Creating state.

What Should I Do If a Workload Remains in the Creating State?

Terminating

A pod is in the Terminating state.

What Should I Do If a Pod Remains in the Terminating State?

Stopped

A pod is in the Stopped state.

What Should I Do If a Workload Is Stopped Caused by Pod Deletion?

Checking the Pod Status

  1. Log in to the CCE console.
  2. Click the cluster name to access the cluster console. In the navigation pane, choose Workloads.
  3. Click the name of the target workload and check the pod statuses.

Checking Pod Configurations

  1. Log in to the CCE console.
  2. Click the cluster name to access the cluster console. In the navigation pane, choose Workloads.
  3. Click the name of the target workload. In the workload pod list, locate the row containing the target pod and choose More > View YAML in the Operation column.

Viewing Pod Events

Method 1

On the CCE console, click the workload name to go to the workload details page, locate the row containing the abnormal pod, and choose More > View Events in the Operation column.

Figure 1 Viewing pod events

Method 2

Use the kubectl command:

kubectl describe pod {pod-name}

Information similar to the following is displayed:

...
Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  49s   default-scheduler  0/2 nodes are available: 2 Insufficient cpu.
  Warning  FailedScheduling  49s   default-scheduler  0/2 nodes are available: 2 Insufficient cpu.

Viewing Container Logs

  1. Log in to the CCE console.
  2. Click the cluster name to access the cluster console. In the navigation pane, choose Workloads.
  3. Locate the row containing the target workload and click View Log in the Operation column.

  4. Switch between pods and containers above the logs.

Logging In to a Container

You can log in to a container using kubectl. For details, see Logging In to a Container.

  1. Log in to the CCE console.
  2. Click the cluster name to access the cluster console. In the navigation pane, choose Workloads.
  3. Click the name of the target workload. In the workload pod list, locate the row containing the target pod and choose More > Remote Login in the Operation column.