Check the cause of failure

You can check the cause of cluster creation failure by viewing the cluster creation events.

Log on to the Resource Orchestration Service (ROS) console.

Select the region where the cluster resides. Then, click Manage at the right of the cluster. In the left-side navigation pane, click Event. Rest the pointer on the failed event to view the specific error message of the failure.


Failure codes and solutions

  • Resource CREATE failed: ResponseException: resources.k8s_SNat_Eip: Elastic IP address quota exceeded Code: QuotaExceeded.Eip

    Solution: Release unused EIPs, or open a ticket to raise the EIP quota.

  • Resource CREATE failed: ResponseException: resources.k8s_master_slb_internet: The maximum number of SLB instances is exceeded. Code: ORDER.QUANTITY_INVALID

    Solution: Release unused SLB instances, or open a ticket to raise the SLB quota.

  • Resource CREATE failed: ResponseException: resources.k8s_vpc: VPC quota exceeded. Code: QuotaExceeded.Vpc

    Solution: Release unused VPCs, or open a ticket to raise the VPC quota.

  • Status Code: 403 Code: InvalidResourceType.NotSupported Message: This resource type is not supported;

    Solution: No ECS in stock or the type is not supported. Select other ECS specifications and try again.

  • Resource CREATE failed: ResponseException: resources.k8s_master_1: The specified image does not support cloud-init. Code: ImageNotSupportCloudInit

    Solution: When a custom image is used to create a cluster, the custom image must be based on the latest CentOS image.

  • Resource CREATE failed: ResponseException: resources.k8s_nodes: The resource is out of stock in the specified zone. Please try other types, or choose other regions and zones. Code: OperationDenied.NoStock

    Solution: The instances of your selected specifications are sold out. Select other availability zones or specifications, and try again.

  • Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway: A route entry already exists, which CIDR is '0.0.0.0/0' Code: RouterEntryConflict.Duplicated

    Solution: Current route table of the VPC includes system route entries. Delete the system route entries, or clear the Configure SNAT for VPC check box, and try again.

  • Resource CREATE failed: ResponseException: resources.KubernetesWorkerRole: The number of role is limited to 200. Code: LimitExceeded.Role

    Solution: The number of RAM roles has reached the quota. Delete some RAM roles, or open a ticket to raise the quota.

  • Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway: The Account failed to create order. Code: OrderFailed

    Solution: Failed to create an order. Open a ticket for consultation.

  • Resource CREATE failed: ResponseException: resources.k8s_master_1: This operation is forbidden by Aliyun RiskControl system. Code: Forbidden.RiskControl

    Solution: An exception occurs to your account. For more information, see What do I do if I get a security notification?.

  • Resource CREATE failed: WaitConditionFailure: resources.k8s_node_cloudinit_wait_cond: See output value for more details.

    Solution: Failed to create a cluster. Try again later, or open a ticket for consultation.

  • Resource CREATE failed: WaitConditionTimeout: resources.k8s_master1_cloudinit_wait_cond: 0 of 2 received:

    Solution: Failed to create a cluster. Try again later, or open a ticket for consultation.

  • Resource CREATE failed: ResponseException: resources.k8s_master_1: The request processing has failed due to some unknown error. Code: UnknownError

    Solution: Unknown error. Try again later, or open a ticket for consultation.

  • Resource CREATE failed: ResponseException: resources.k8s_nodes: The request processing has failed due to some unknown error. Code: UnknownError

    Solution: Unknown error. Try again later, or open a ticket for consultation.