How Can I Handle an AS Group Exception?

The handling method varies depending on the possible cause.

• Issue description: insufficient quota for ECSs, EVS disks, or EIPs

  Possible cause: insufficient quota

  Handling method: increase the quota or delete unnecessary resources, and then enable the AS group.

• Issue description: The VPC, security group, or subnet does not exist.

  Possible cause: The VPC service encounters an exception or resources have been deleted.

  Handling method: Wait until the VPC service recovers, or modify parameters of the VPC, security group, and subnet in the AS group, and then enable the AS group.

• Description: The load balancing listener or load balancer is unavailable.

  Possible cause: The ELB service encounters an exception or resources have been deleted.

  Handling method: Wait until the ELB service recovers, or modify load balance parameters in the AS group, and then enable the AS group.

• Issue description: The image used by the AS configuration does not exist or the key pair does not exist.

  Possible cause: Resources have been deleted.

  Handling method: Change the AS configuration for the AS group and then enable the AS group.

• Issue description: The notification subject configured for your lifecycle hook does not exist.

  Possible cause: The notification theme is deleted after the scaling activity starts.

  Handling method: Change a notification theme and enable the AS group.

• Issue description: The subnet you select does not have enough private IP addresses.

  Possible cause: Private IP addresses in the subnet used by the AS group have been used up.

  Handling method: Modify the subnet information and enable the AS group.

• Issue description: The ECS resources of this type in the selected AZ have been sold out.

  Possible cause: ECSs of this type have been sold out or are not supported in the AZ selected for the AS group. ECSs of this type are the ECS flavor selected in the AS configuration.

  Handling method: Change the AS configuration for the AS group and then enable the AS group. If there is no instance in the AS group, you can also change the AZ for the AS group and then enable the AS group.

• Description: The selected specifications and the disk do not match.

  Possible cause: The ECS type in the AS configuration does not match the disk type, leading to the ECS creation failure.

  Handling method: Change the AS configuration for the AS group and then enable the AS group.

• Issue description: Storage resources of this type have been sold out in the selected AZ.

  Possible cause: Storage resources of this type have been sold out or are not supported in the AZ selected for the AS group. Storage resources of this type refer to the system and data disk types selected for the AS configuration.

  Handling method: Change the AS configuration for the AS group and then enable the AS group. If there is no instance in the AS group, you can also change the AZ for the AS group and then enable the AS group.

• Description: The parameters for creating an ECS are invalid.

  Possible cause: Certain parameters in the AS configuration are invalid, or the EIP quota is insufficient, leading to the ECS creation failure.

  Handling method: Change the AS configuration for the AS group and then enable the AS group. If the EIP quota is insufficient, apply for a higher quota or delete idle resources, and then enable the AS group.

• Issue description: The system is abnormal.

  Handling method: Try again later or contact technical support.