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.
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. |
|
Node Pool FAQs
- What Should I Do If a Node Pool Is Abnormal?
- What Should I Do If No Node Creation Record Is Displayed When the Node Pool Is Being Expanding?
- What Should I Do If a Node Pool Scale-Out Fails?
- What Should I Do If Some Kubernetes Events Fail to Display After Nodes Were Added to or Deleted from a Node Pool in Batches?
- How Do I Modify ECS Configurations When an ECS Cannot Be Managed by a Node Pool?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore