All Products
Search
Document Center

Troubleshoot the Failure to Create an ACK Cluster

Last Updated: May 12, 2021

Overview

This document describes how to troubleshoot the failure to create a Container Service for Kubernetes (ACK) cluster.

Details

You can perform the following steps to view the error message of the failure to create an ACK cluster based on cluster logs, and fix the issue by using the corresponding solution:

  1. Log on to the ACK console. Find the cluster that you require and click View Logs in the Actions column to view the error message.
  2. Fix the issue by using the solution that corresponds to the error message. The following table describes the error messages and corresponding solutions.
    Error message Solution
    Resource CREATE failed: ResponseException: resources.k8s_SNat_Eip: Elastic IP address quota exceeded Code: QuotaExceeded.Eip Release idle elastic IP addresses (EIPs) or submit a ticket to increase the quota of EIPs.
    Resource CREATE failed: ResponseException: resources.k8s_master_slb_internet: The maximum number of SLB instances is exceeded. Code: ORDER.QUANTITY_INVALID Release idle Server Load Balancer (SLB) instances or submit a ticket to increase the quota of SLB instances.
    Resource CREATE failed: ResponseException: resources.k8s_vpc: VPC quota exceeded. Code: QuotaExceeded.Vpc Release idle virtual private clouds (VPCs) or submit a ticket to increase the quota of VPCs.
    Status Code: 403 Code: InvalidResourceType.NotSupported Message: This resource type is not supported This error occurred because the selected Elastic Compute Service (ECS) instance type is unavailable or not supported. Select another ECS instance type and try again.
    Resource CREATE failed: ResponseException: resources.k8s_master_1: The specified image does not support cloud-init. Code: ImageNotSupportCloudInit To create a cluster from a custom image, make sure that the image is based on the latest CentOS.
    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 The selected instance type is unavailable in the specified zone. Select another instance type or change the zone.
    Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway: A route entry already exists, which CIDR is '0.0.0.0/0' Code: RouterEntryConflict.Duplicated A default route exists in the route table of the selected VPC. Delete the default route or clear Configure SNAT for VPC and try again.
    Resource CREATE failed: ResponseException: resources.KubernetesWorkerRole: The number of role is limited to 100. Code: LimitExceeded.Role RequestId: CA59BB8C-5F21-4146-A468-6D4601A55F39:"" The number of RAM roles has reached the quota limit. Delete idle RAM roles or submit a ticket to increase the quota of RAM roles.
    Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway: The Account failed to create order. Code: OrderFailed The error occurred when the system creates the order. Submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: ResponseException: resources.k8s_master_1: This operation is forbidden by Aliyun RiskControl system. Code: Forbidden.RiskControl Your account is at risk. Submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: ResponseException: resources.k8s_master_slb_internet: Your account does not have enough balance. Code: PAY.INSUFFICIENT_BALANCE To create pay-as-you-go instances, your account balance must be more than CNY 100. Add funds to your account first.
    Resource CREATE failed: ResponseException: resources.k8s_nodes: Your account does not have enough balance. Code: InvalidAccountStatus.NotEnoughBalance
    Resource CREATE failed: WaitConditionFailure: resources.k8s_node_cloudinit_wait_cond: See output value for more details. The cluster configuration is invalid. Try again later or submit a ticket.
    Resource CREATE failed: WaitConditionTimeout: resources.k8s_master1_cloudinit_wait_cond: 0 of 2 received:
    Resource CREATE failed: ResponseException: resources.k8s_master_1: The request processing has failed due to some unknown error. Code: UnknownError An unknown error occurred. Try again later or submit a ticket.
    Resource CREATE failed: ResponseException: resources.k8s_nodes: The request processing has failed due to some unknown error. Code: UnknownError
    code:"InsufficientBalance.AgentCredit", msg:"Insufficient agent credit. Please contact your agent." The account balance is insufficient. Check the bill.
    Resource CREATE failed: ResponseException: resources.k8s_SNat_Eip: The account is arrearage. Code: ORDER.ARREARAGE The account balance is insufficient. Check the bill.
    "errorCode":"ErrManagedAddonRoleNotAttach","errorMsg":"please complete the cluster addon's service ramrole authorization at https://ur.alipay.com/1paTcxSWdAEW70GVH5TZiO,reqId=85DCCF3D-1E34-4E35-90A7-F4DB7A4488DC" Required permissions must be granted to the service. Log on to the Resource Access Management (RAM) console and grant the required permissions.

    Resource CREATE failed: WaitConditionFailure: resources.k8s_node_cloudinit_wait_cond: See output value for more details.;See output value for more details.;See output value for more details.:Feb 17 17:20:14 iZ2zXXXaysvZ cloud-init: [discovery] Failed to connect to API Server "192.168.1.43:6443": token id "96f757" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

    Feb 17 17:20:19 iZ2zXXXaysvZ cloud-init: [discovery] Trying to connect to API Server "192.XX.XX.43:6443"

    Feb 17 17:20:19 iZ2zXXXaysvZ cloud-init: [discovery] Created cluster-info discovery client, requesting info from "https://192.XX.XX.43:6443"

    Feb 17 17:20:19 iZ2zXXXaysvZ cloud-init: [discovery] Failed to connect to API Server "192.XX.XX.43:6443": token id "96f757" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

    Feb 17 17:20:24 iZ2zXXXaysvZ cloud-init: [discovery] Trying to connect to API Server "192.XX.XX.43:6443"

    Feb 17 17:20:24 iZ2zXXXaysvZ cloud-init: [discovery] Created cluster-info discovery client, requesting info from "https://192.XX.XX.43:6443"

    Feb 17 17:20:24 iZ2zXXXaysvZ cloud-init: [discovery] Failed to connect to API Server "192.XX.XX.43:6443": token id "96f757" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

    Feb 17 17:20:29 iZ2zXXXaysvZ cloud-init: [discovery] Trying to connect to API Server "192.XX.XX.43:6443"

    Feb 17 17:20:29 iZ2zXXXaysvZ cloud-init: [discovery] Created cluster-info discovery client, requesting info from "https://192.XX.XX.43:6443"

    Feb 17 17:20:29 iZ2zXXXaysvZ cloud-init: [discovery] Failed to connect to API Server "192.XX.XX.43:6443": token id "96f757" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

    Feb 17 17:20:34 iZ2zXXXaysvZ cloud-init: [discovery] Trying to connect to API Server "192.XX.XX.43:6443"

    Feb 17 17:20:34 iZ2zXXXaysvZ cloud-init: [discovery] Created cluster-info discovery client, requesting info from "https://192.XX.XX.43:6443"

    Feb 17 17:20:34 iZ2zXXXaysvZ cloud-init: [discovery] Failed to connect to API Server "192.XX.XX.43:6443": token id "96f757" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

    Feb 17 17:20:39 iZ2zXXXaysvZ cloud-init: [discovery] abort connecting to API servers after timeout of 5m0s

    Feb 17 17:20:39 iZ2zXXXaysvZ cloud-init: couldn't validate the identity of the API Server: abort connecting to API servers after timeout of 5m0s

    Feb 17 17:20:39 iZ2zXXXaysvZ cloud-init: + on_exit

    Feb 17 17:20:39 iZ2zXXXaysvZ cloud-init: + '[' 1 -eq 0 ']'

    Feb 17 17:20:39 iZ2zXXXaysvZ cloud-init: ++ cat /var/log/messages

    Feb 17 17:20:39 iZ2zXXXaysvZ cloud-init: ++ grep cloud-init

    Feb 17 17:20:39 iZ2zXXXaysvZ cloud-init: ++ tail -n 20

     

    Addition: public network seems ok.

    Log on to the corresponding ECS instance, collect diagnostics data, and then troubleshoot the issue based on the diagnostics data. For more information, see How do I collect diagnostics data from nodes in an ACK cluster? If the issue persists, submit a ticket.
    code:"InvalidResourceType.NotSupported", msg:"This resource type is not supported. Please try other resource types." The specified instance type is unavailable. We recommend that you change the instance type or select multiple instance types.
    Resource CREATE failed: ResponseException: resources.k8s_nodes_config: The instance type "\"ecs.cm4.2xlarge\"" is not supported by ess. Code: InvalidInstanceType.NotSupported
    code:"Zone.NotOnSale", msg:"The resource in the specified zone is no longer available for sale. Please try other regions and zones."
    code:"OperationDenied.NoStock", msg:"The resource is out of stock in the specified zone. Please try other types, or choose other regions and zones."
    Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway: The Account is rejected by risk control system. Code: RISK.RISK_CONTROL_REJECTION Your account is at risk. Submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway: The Account failed to create order. Code: CreateOrderFailed The network address translation (NAT) gateway failed to be created. Submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway_SNATEntry: The Eip not in nat gateway Code: EIP_NOT_IN_GATEWAY The EIP failed to be associated with the NAT gateway. We recommend that you recreate a cluster.
    Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway_SNATEntry: The NatGateway instance not exist. Code: InvalidNatGatewayId.NotFound The NAT gateway instance does not exist. We recommend that you recreate a cluster.
    Resource CREATE failed: ResponseException: resources.k8s_master_slb_Eip: Request was denied due to conflict with a previos request. Code: OperationConflict The EIP failed to be created. We recommend that you recreate a cluster.
    Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway: vpc incorrect status. Code: InvalidVPCStatus Submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: ResponseException: resources.k8s_SNat_Eip: Reserve eip failed. Code: ReserveIpFail Source NAT (SNAT) failed to be configured. We recommend that you recreate a cluster.
    Resource CREATE failed: RetryError: resources.k8s_master_1: RetryError[step check_instance_ids_is_ready failed]: The startup of the ECS instance timed out. We recommend that you recreate a cluster.
    code:"Instance.StartInstanceFailed", msg:"Instances starting failed."
    code:"InvalidInstanceType.ValueUnauthorized", msg:"The specified InstanceType is not authorized." Submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: ResponseException: resources.k8s_sg_default_ingress: The specified SecurityGroupId does not exist. Code: InvalidSecurityGroupId.NotFound The ID of the security group is invalid.
    Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway_SNATEntry: Operation failed because Some ips in SnatIpPool are not added in CommonBandwidthPackage. Code: OperationFailed.SnatIpsCheck Submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: ResponseException: resources.k8s_master_2: The specified InstanceId does not exist. Code: InvalidInstanceId.NotFound
    Resource CREATE failed: ResponseException: resources.k8s_master_ssh_internet_vgroup: The specified BackendServers is invalid; some of the specified backend servers do not exist or are not running. Code: ObtainIpFail The backend server failed to be configured for the SLB instance. We recommend that you recreate a cluster.
    Resource CREATE failed: ResponseException: resources.k8s_master_slb_listener: Request was denied due to request throttling. Code: Throttling The API request was denied due to throttling. Submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: WaitConditionTimeout: resources.k8s_master1_cloudinit_wait_cond: 0 of 2 received:

    The script failed to be deployed. Log on to the corresponding ECS instance and run the following command to obtain the log for troubleshooting:

    grep cloud-init /var/log/messages | tee /tmp/attach.log
    Resource CREATE failed: StackValidationFailed: resources.k8s_NAT_Gateway: Property error: k8s_NAT_Gateway.Properties.VpcId: vpc-xxx is not exists.: The VPC does not exist. Check whether the VPC exists.
    Wait for ce474bf60019e43e99f975865f43874a5 Waitfor cluster master ready timeout, Error code: ErrWaitForClusterReady The master node failed to be created in the managed Kubernetes cluster. Submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: ResponseException: resources.k8s_master_slb_Eip: The instance component is invalid. Code: COMMODITY.INVALID_COMPONENT RequestId: AD2DCCA5-09F4-4BE0-B593-EDA8070C8F13: The EIP is unavailable. Submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: ResponseException: resources.k8s_SNat_Eip: eip frequent purchase Code: FrequentPurchase.EIP RequestId: 459A27DD-AD46-4D15-A3FB-2C744B69B4CB: Throttling is imposed for purchasing EIPs. Recreate a cluster later.
    code:\"QuotaExceeded.PrivateIpAddress\", msg:\"The specified VSwitch \"vsw-2ze6trd5pz8w5skvsevib\" has not enough IpAddress. The number of remaining private IP addresses of the vSwitch is insufficient. We recommend that you use a vSwitch that has sufficient private IP addresses.
    Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway: NatGateway in one vpc support only one. Code: VPC_ONLY_CAN_CREATE_ONE_NAT_GATEWAY RequestId: A33F3E64-C2A1-44D0-BCEF-30B1B89216F5: The error occurred due to concurrent operations. Recreate a cluster later.
    Resource CREATE failed: ResourceCreateFailed: resources.k8s_master_1: Resource "k8s_master_1" creation failed,instances(i-bp1XXX51gak) were deleted unexpectedly.: The ECS instance does not exist. We recommend that you recreate a cluster or submit a ticket.
    Resource CREATE failed: ResponseException: resources.k8s_NAT_Gateway_Bind_Eip: instance not found Code: InvalidParams.NotFound RequestId: E01D9801-60D3-4B0B-B14C-B32CC704A9ED: The EIP does not exist. We recommend that you recreate a cluster or submit a ticket.
    code:"InvalidInstanceType.ValueNotSupported", msg:"The specified instanceType exceeds the maximum limit for the POSTPaid instances." The ECS instance of the specified type cannot be created. We recommend that you submit a ticket to contact Alibaba Cloud technical support.
    code:"InvalidParameter.Encrypted.KmsNotEnabled", msg:"The encrypted disk need enable KMS" The ECS instance of the specified type cannot be created. We recommend that you submit a ticket to contact Alibaba Cloud technical support.
    Resource CREATE failed: ResponseException: resources.k8s_nodes_config: The specified keyPairName does not exist. Code: InvalidKeyPairName.NotFound RequestId: F1B1E00F-D031-449E-A9C7-FACF89F7F08F:"" The key pair that corresponds to the ECS instance does not exist. Add the key pair in the ECS console.
    Resource CREATE failed: ResponseException: resources.k8s_nodes_sg: The previous request is still processing. Code: IDEMPOTENCE_PROCESSING RequestId: E46652E8-C0CA-4B4A-BC25-CCBEE6B63DE1: Scaling groups cannot be concurrently created in Auto Scaling. Recreate a cluster.
    Resource CREATE failed: ResponseException: resources.k8s_sg: The specified Tag.n.Key is not valid. Code: InvalidTagKey.Malformed RequestId: 978F1855-7AE7-4A71-9A88-DD113A11574B: The tag key is invalid. Modify it.
    code:"InstanceType.Offline", msg:"The specified InstanceType has been offline." The ECS instance type is unavailable. Change the ECS instance type.
    Resource CREATE failed: ResponseException: resources.k8s_nodes_sg: Ess should be authorized in ram to operate user resource. Code: UserNotAuthorizeEss RequestId: 5F03E964-F9F3-4FBD-B825-678B6CC7FA62: Activate Auto Scaling and grant the required permissions to Auto Scaling.
    code:"AccountForbidden.ProductCreationLimited", msg:"The commodity must be officially operated by Aliyun and in pay-as-you-go billing method." The current account can purchase only pay-as-you-go instances.
    Resource CREATE failed: ResponseException: resources.k8s_nodes: The specified zone does not support vpc network or sold out. Code: ResourceNotAvailable.VPCNetwork RequestId: 380D5E72-0AF3-48C1-B93B-4DF9FC0D3A05: The instance type is unavailable in the specified region. Change the instance type or region.
    Resource CREATE failed: ResponseException: resources.k8s_nodes_sg: The specified virtual switch does not exist. Code: InvalidVSwitchId.NotFound RequestId: 7DAFB4B1-1B3E-4341-BEE7-F3E0F69AD170: The vSwitch does not exist or Auto Scaling is not granted the required permissions.
    Resource CREATE failed: ResponseException: resources.k8s_nodes_config: The specified value of parameter "SystemDiskSize" is not valid. Code: InvalidParameter RequestId: 5E60376B-CB7D-4786-B48F-8C176FD07104: The size of the system disk is invalid.
    Resource CREATE failed: ResponseException: resources.KubernetesWorkerRole: The number of role is limited to 100. Code: LimitExceeded.Role RequestId: CA59BB8C-5F21-4146-A468-6D4601A55F39:"" The number of RAM roles has reached the upper limit.
    Resource CREATE failed: ResponseException: resources.k8s_nodes_sg: The current status of virtual switch does not support this operation. Code: IncorrectVSwitchStatus RequestId: 38C98BCF-D849-4AFF-9866-D81C1332A7FF:"" The status of the vSwitch is abnormal. We recommend that you submit a ticket to contact Alibaba Cloud technical support.
    "code":"ZoneNotSupported","message":"ThecurrentzonedoesnotsupportcreatingSLB,pleasetryotherzones","requestId":"FE89A22B-DE75-4DBD-8909-FB0A64ECDA8E","status":400 SLB instances cannot be created in the specified zone. Change the zone.
    Resource CREATE failed: ResponseException: resources.k8s_nodes_sg: Don't have permission to access this API. Code: Forbidden.Unsubscribed RequestId: 5B508CCB-D091-465B-9509-6744BC18421A:"" Auto Scaling is not activated or granted the required permissions. Log on to the Auto Scaling console for authorization. For more information, see Manage the Auto Scaling service linked role.
    Failed to scale cluster by ESS, err: {Reson : A user requests to execute scaling rule "asr-xxx", changing the Total Capacity from "7" to "8". , Description : Add "1" ECS instance , Detail : Fail to create Instances into scaling group(code:"InvalidParameter.NotMatch", msg:"the provided 'Rule -> instance_type_family: include[ecs.ebmg6a ecs.ebmr6a ecs.ebmc6a]' and 'InstanceType -> instance_type_family: ecs.sn2ne' are not matched.") The aliyun_2_1903_x64_20G_uefi_alibase_20200616.vhd image you selected supports only the ecs.ebmg6a, ecs.ebmr6a, and ecs.ebmc6a instance types. Change the image or instance type.
    Resource CREATE failed: RetryError: resources.k8s_master_1: RetryError[step check_instance_is_running failed]: The startup of the ECS instance timed out. Try again.
    Resource CREATE failed: ResponseException: resources.k8s_nodes_config: The specified value of parameter "SystemDiskSize" is not valid. Code: InvalidParameter RequestId: 2D03F614-6B1A-43B1-879A-D41D17961945: The size of the system disk is invalid. Adjust the size of the system disk to 40 to 500 GB.
    {\"code\":\"VpcNotFound\",\"message\":\"The VPC vpc-zm0ug0jzr7l1qy2by6xft not exist\",\"requestId\":\"EA588CCB-69BF-4A42-8D9B-EF62B4772787\",\"status\":400} The VPC does not exist or the AliyunCSDefaultRole role is not assigned. You can check whether the AliyunCSDefaultRole role is assigned and the required policies are attached to the role in the RAM console. If not, assign the role and attach the required policies. For more information, see the AliyunCSDefaultRole section of the ACK default roles topic.

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

    Jun 25 05:54:23 AliYun cloud-init: + public::common::log '--endpoint must be provided! eg. 192.X.X.1:XX'

    Log on to the corresponding ECS instance, collect diagnostics data, and then troubleshoot the issue based on the diagnostics data. For more information, see How do I collect diagnostics data from nodes in an ACK cluster? If the issue persists, submit a ticket.

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

    Feb 4 18:04:46 bj-mtaq-k8s-image-prod-001 cloud-init: wait for port 22 ready failed.

    Port 22 of the master node is disabled. We recommend that you submit a ticket to contact Alibaba Cloud technical support.

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

    Oct 23 08:11:16 iZufXXX68z2lZ cloud-init: [ERROR ImagePull]: failed to pull image registry-vpc.ap-south-1.aliyuncs.com/acs/coredns:1.2.2: output: Error response from daemon: Gethttps://regiXXXuncs.com/v2/acs/coredns/manifests/1.2.2:Gethttps://dockXXXyuncs.com/auth?scope=repository%3Aacs%2Fcoredns%3Apull&service=registry.aliyuncs.com%3Aap-south-1%3A26842:net/http: request canceled (Client.Timeout exceeded while awaiting headers)

    Image pulling timed out. We recommend that you submit a ticket to contact Alibaba Cloud technical support.

    Resource CREATE failed: WaitConditionFailure: resources.k8s_master_cloudinit_wait_cond: See output value for more details.:Feb 18 18:01:27 iZufXXXz2lZ cloud-init: + docker pull registry-vpXXXcs.com/acs/kube-apiserver:v1.14.8-aliyun.1

    Feb 18 18:01:42 iZufXXX68z2lZ cloud-init: Error response from daemon: Gethttps://regXXX-gov-1.aliyuncs.com/v2/:net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

    Error message Solution


    Resource CREATE failed: WaitConditionFailure: resources.k8s_master_cloudinit_wait_cond: See output value for more details.:Nov 14 12:42:11 iZufXXXl68z2lZ cloud-init: + '[' 1 '!=' 0 ']'

    Nov 14 12:42:11 iZufXXXz2lZ cloud-init: + [[ -n --version v2.14.1 ]]

    Nov 14 12:42:11 iZuXXXlZ cloud-init: + echo 'Failed to install helm with the arguments provided: --version v2.14.1'

    Helm failed to be installed. Recreate a cluster.

    Resource CREATE failed: WaitConditionFailure: resources.k8s_master_cloudinit_wait_cond: See output value for more details.:Nov 14 08:37:21 iZuXXXz2lZ cloud-init: ++ date '+[%Y%m%d %H:%M:%S]: '

    Nov 14 08:37:21 iZuf6XXXz2lZ cloud-init: + echo '[20191114' '08:37:21]:' local file run-Kubernetes.tar.gz does not exist, trying to download from '[]'

    The pulling of the deployment package timed out. Recreate a cluster.

    Resource CREATE failed: WaitConditionFailure: resources.k8s_node_cloudinit_wait_cond: See output value for more details.:Nov 21 22:27:56 iZuf6XXX8z2lZ cloud-init: cloud-init: + kubeadm join --node-name eu-central-1.192.X.X.24 --token xxx.xxxx 192.X.X.13:6443 --discovery-token-unsafe-skip-ca-verification

    Nov 21 22:32:56 iZufXXX68z2lZ cloud-init: error execution phase preflight: couldn't validate the identity of the API Server: abort connecting to API servers after timeout of 5m0s

    The API Server cannot be connected to. Recreate a cluster.

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

    Feb 4 15:35:10 iZuf6XXX8z2lZ cloud-init: Failed to start ntpd.service: Unit not found.

    The Network Time Protocol daemon (ntpd) failed to be started. Recreate a cluster.

    Resource CREATE failed: WaitConditionFailure: resources.k8s_master_cloudinit_wait_cond: See output value for more details.:Nov 14 08:37:21 iZufXXXz2lZ cloud-init: + curl --retry 10 --retry-delay 5 -sSLhttp://aliacs-kXXXng-internal.aliyuncs.com/public/pkg/run/run-Kubernetes.tar.gz

    Nov 14 08:37:21 iZufXXX8z2lZ cloud-init: + tar -xvf run-Kubernetes.tar.gz

    Nov 14 08:37:21 iZuf6XCXX2lZ cloud-init: tar: This does not look like a tar archive

    The installation package failed to be downloaded. Recreate a cluster.

    Failed to create resource SDK.ServerError ErrorCode: Forbidden Recommend: RequestId: 7D76D1F3-A864-4B23-B96C-6CC6F0AF7DCC Message: User not authorized to operate on the specified resource., Error code: ErrCreateLoadBanlancer, Request id: 9BBF60B9-69E9-4696-801C-5D83E14E96B3

    The current account is not authorized to call the CreateLoadBanlancer operation. The common reason is that the AliyunCSDefaultRolePolicy policy is modified.

    Delete the AliyunCSDefaultRole role in the RAM console and assign the role again.

    error: service role not attach, Error code: ErrKubernetesAuditRoleNotAttach

    New users must assign their Alibaba Cloud accounts the default roles to use ACK. To authorize RAM users to use ACK, new users must log on to the RAM console and grant permissions to the RAM users. For more information, see ACK default roles.

    Nov 11 15:14:51 iZ2zXXXaysvZ cloud-init: + ssh -e none root@10.XX.XX.164 'tar xf run-1.18.8-aliyun.1.tar.gz'

    Nov 11 15:14:51 iZ2zXXXaysvZ cloud-init: + for host in '$NODES'

    Nov 11 15:14:51 iZ2zXXXaysvZ cloud-init: + [[ 10.XX.XX.165 == \1\0\.\2\5\4\.\5\0\.\1\6\6 ]]

    Nov 11 15:14:51 iZ2zXXXaysvZ cloud-init: + public::common::log 'copy scripts:10.254.50.165'

    Nov 11 15:14:51 iZ2zXXXaysvZ cloud-init: ++ date '+[%Y%m%d %H:%M:%S]: '

    Nov 11 15:14:51 iZ2zXXXaysvZ cloud-init: + echo '[20201111' '15:14:51]:' copy scripts:10.XX.XX.165

    Nov 11 15:14:51 iZ2zXXXaysvZ cloud-init: [20201111 15:14:51]: copy scripts:10.XX.XX.1 65

    Nov 11 15:14:51 iZ2zXXXaysvZ cloud-init: + scp run-1.18.8-aliyun.1.tar.gz root@10.XX.XX.165:/root/

    Nov 11 17:16:51 iZ2zXXXaysvZ cloud-init: ssh_exchange_identification: read: Connection reset by peer

    Nov 11 17:16:51 iZ2zXXXaysvZ cloud-init: lost connection

    Package copy timed out due to network issues. Recreate a cluster.

Applicable scope

  • ACK