Help Center> Cloud Container Engine> FAQ> Workload> Workload Abnormalities> What Should I Do If a Workload Remains in the Creating State?
View PDF

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

Symptom

After the node is changed, the workload on the node is always in the creating state.

Solution

  1. Log in to the node (ECS) through VNC or SSH and delete the cpu_manager_state file. For details on how to log in to the node, see Logging In to a Linux ECS.

    Example command for deleting the file:

    rm -rf /mnt/paas/kubernetes/kubelet/cpu_manager_state

  2. Restart the node or kubelet. The following is the kubelet restart command: 

    systemctl restart kubelet

    Verify that workloads on the node can be successfully restarted or created.

    For details, see What Should I Do If I Fail to Restart or Create Workloads on a Node After Modifying the Node Specifications?.

Submitting a Service Ticket

If the problem persists, submit a service ticket.

Parent topic: Workload Abnormalities