Help Center> Cloud Container Engine> FAQ> Workload> Workload Abnormalities> How Do I Use Events to Fix Abnormal Workloads?
View PDF

How Do I Use Events to Fix Abnormal Workloads?

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

Table 1 Troubleshooting methods

Pod Status

Event Information

Solution

Pending

Failed to schedule pods.

For details, see What Should I Do If Pod Scheduling Fails?.

ImagePullBackOff

Failed to pull the image.

For details, see What Should I Do If a Pod Fails to Pull the Image?.

CreateContainerError

CrashLoopBackOff

Failed to start containers.

For details, see What Should I Do If Container Startup Fails?.

Evicted

The pod status is Evicted, and the pod keeps being evicted.

For details, see What Should I Do If a Pod Fails to Be Evicted?.

Pending

The storage volume fails to be mounted to the pod.

For details, see What Should I Do If a Storage Volume Cannot Be Mounted or the Mounting Times Out?.

Creating

The pod stays Creating.

For details, see What Should I Do If a Workload Remains in the Creating State?.

Terminating

The pod stays Terminating.

For details, see What Should I Do If Pods in the Terminating State Cannot Be Deleted?.

Stopped

The pod is in the Stopped state.

For details, see What Should I Do If a Workload Is Stopped Caused by Pod Deletion?.

Viewing Pod Events

Run the kubectl describe pod podname command to view pod events, or log in to the CCE console and view pod events on the workload details page.

$ kubectl describe pod prepare-58bd7bdf9-fthrp
...
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.
Figure 1 Viewing pod events
Parent topic: Workload Abnormalities