Help Center> Cloud Container Engine> FAQ> Node> Specification Change> What Should I Do If I Fail to Restart or Create Workloads on a Node After Modifying the Node Specifications?
View PDF

What Should I Do If I Fail to Restart or Create Workloads on a Node After Modifying the Node Specifications?

Context

In clusters of Kubernetes v1.13.6, the kubelet option cpu-manager-policy defaults to static, allowing pods with certain resource characteristics to be granted increased CPU affinity and exclusivity on the node. If you modify CCE node specifications on the ECS console, the original CPU information does not match the new CPU information. As a result, workloads on the node cannot be restarted or created.

For more information, see Control CPU Management Policies on the Node.

Impact

Clusters of Kubernetes v1.13.6 and v1.13.7 and clusters with the CPU management policy enabled will be affected.

Solution

  1. Log in to the node (ECS) using 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 the file deletion: 
    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

  3. Verify that workloads on the node can be successfully restarted or created.
Parent topic: Specification Change