Phenomenon
When a scaling activity is being executed, there may be some reasons that cause the activity to fail, which require timely attention and processing to ensure that the scaling activity proceeds normally.
You can view the scaling group state in the scaling group list. If your scaling group state shows 
, the latest scaling activity in this scaling group has failed.
Note:
You can hover the mouse pointer over the prompt icon to view the specific cause of the exception.
Analysis
Viewing Reason Explanation
AS provides an intelligent way to view the reasons for scaling group activity failures. You can view detailed information about scaling activity failures by performing the following steps:
- Click the ID of the scaling group where the scaling activity failed in the scaling group list.
- On the scaling group details page, select Scaling Activities to view activity information.
Performing Corresponding Operations According to the Prompts
You can perform corresponding operations based on the reason why the scaling activity failed. Common reasons for scaling activity failure are as follows.
Reasons for the Failure of Scaling Activities
The reasons for the failure of scaling activities can be divided into the following categories:
- CVM Related
- Image Related
- Network Related
- Cloud Block Storage Related
- CLB Related
Troubleshooting
CVM Related
CVM Sold Out
Failure Reason: Insufficient inventory of the specified resource.
Solution: You can configure multi-models in the launch configuration and select other instance specifications.
The CVM Model is Invalid in the Current Availability Zone
Failure Reason: The specified instance specification is offline.
Solution: Select the instance specification on sale in the launch configuration.
The CVM Does Not Work with Cloud Block Storage
Failure Reason: The current system disk type does not support this model instance.
Solution: Check the scaling configuration and change the system disk type. It is recommended that you choose a high-performance cloud disk or SSD cloud disk.
Insufficient CVM Purchase Quota
Failure Reason: Each user has a quota for purchasing CVMs.
If you exceed this quota, AS cannot open the machine.
Solution: Reduce the number of sub-machines for scaling-out.
The CVM Model Does Not Exist
Failure Reason: The model defined in your launch configuration is incorrect or has been removed from the shelves.
Solution: Replace the corresponding launch configuration.
Image Related
The Image Does Not Exist
Failure Reason: The image may no longer exist or is invalid.
Solution: Check the relevant configuration in the launch configuration.
The Image Exceeds the System Disk Capacity
Failure Reason: The system disk capacity is less than the image file size.
Solution: Check the launch configuration, increase the system disk capacity, or use an image that occupies a smaller space.
Network Related
Only Supports VPC
Failure Reason: A model that only supports VPC was selected in the launch configuration.
Solution: Do not use this model in the basic network; deselect it in the launch configuration.
The number of IP addresses in the VPC subnet is less than the number of instances to be scaled-out.
Failure Reason: The number of IP addresses in the VPC subnet is limited.
Solution: Create a new subnet and expand its subnet IP range (CIDR).
Issues Related to Cloud Block Storage
Cloud Disk Sold Out
Failure Reason: Insufficient inventory of the specified resource.
Solution: Configure the default cloud disk feature in the launch configuration.
The CVM Does Not Work with Cloud Block Storage
Failure Reason: The current system disk type does not support this model instance.
Solution: Check the scaling configuration and change the system disk type. It is recommended that you choose a high-performance cloud disk or SSD cloud disk.
Issues Related to CLB
CLB Does Not Exist
Failure Reason: The CLB may no longer exist or is invalid. Check the relevant configuration in the CLB.
Solution: Make sure that the CLB instance associated with the scaling group is working properly.
Listener Does Not Exist
Failure Reason: The listener in the CLB may no longer exist or is invalid. Check the relevant configuration in the CLB.
Solution: Make sure that the CLB instance associated with the scaling group is working properly.
The Forwarding Path Does Not Exist
The listener in the load balancer forwards to the specified domain name/URL path. The domain name/URL path you created may no longer exist or is invalid. Please check the relevant configuration in load balancing.
Solution: Make sure that the CLB associated with the scaling group is working properly.
The Specified CLB Is Busy
Failure Reason: The CLB task is in progress.
Solution: It is recommended that manual operations be reduced when the scaling group is active to avoid operation mutual exclusion.