Help Center/ Cloud Container Engine/ FAQs/ Node Pool/ What Should I Do If a Node Pool Is Abnormal?
Updated on 2024-07-13 GMT+08:00
View PDF

What Should I Do If a Node Pool Is Abnormal?

Fault Locating

Locate the fault based on the status of the abnormal node pool, as shown in Table 1.

Table 1 Node pool exceptions

Abnormal Node Pool Status

Description

Solution

Error

The node pool cannot be deleted.

Delete the node pool again. If the node pool still cannot be deleted, submit a service ticket and delete the node pool.

QuotaInsufficient

The node pool cannot be scaled out due to insufficient quota.

Submit a service ticket and increase the quota.

SoldOut

The underlying resources are insufficient.

Update the node pool configuration and select other available resources.

ConfigurationInvalid

The ECS group does not exist (ServerGroupNotExists).

The ECS group to which the node pool belongs is not present. This may be because you manually deleted the ECS group.
  1. Log in to the CCE console. In the navigation pane, choose Nodes, click the Node Pools tab, and click the name of the target node pool. Click the Overview tab, click Expand, and check the ECS group to which the node pool belongs.
  2. Log in to the ECS console. In the navigation pane, choose Elastic Cloud Server > ECS Group and see if the target ECS group is present.
  3. If the ECS group is not present, log in to the CCE console. In the navigation pane, choose Nodes, click the Node Pools tab, locate the row containing the target node pool, and click Update. In the Advanced Settings area, unbind or change the ECS group.
Parent Topic: Node Pool