Skip to content

Exclude cn-north-1d AZ when creating EKS cluster in China Beijing region #3916

New issue
New issue
Closed
#3947
#3920
Closed
Exclude cn-north-1d AZ when creating EKS cluster in China Beijing region#3916
#3947
#3920
Labels
kind/bug
@walkley

Description

@walkley
walkley
opened on Jun 30, 2021

Background

AWS launched the 3rd AZ(cn-north-1d) in Beijing region on Jun 6th. These is a known issue that EKS cluster will be failed to create if specified subnets in cn-north-1d for VPC config parameters.

What were you trying to accomplish?

  1. Creating EKS clusters with default parameters(e.g. eksctl create cluster --name test1), eksctl will pick all AZs by default.
  2. Creating EKS clusters with specified AZs including cn-north-1d

What happened?

Failed to create EKS cluster with error message "Cannot create cluster 'bjs-test' because cn-north-1d, the targeted availability zone, does not currently have sufficient capacity to support the cluster...", you may refer to the logs in below for detail error messages.

How to reproduce it?

  1. eksctl create cluster --name bjs-test --region cn-north-1
  2. eksctl create cluster --name bjs-test --zones cn-north-1a,cn-north-1b,cn-north-d --region cn-north-1

Logs

$ eksctl create cluster --name bjs-test --without-nodegroup --region cn-north-1
2021-06-30 08:53:19 [ℹ]  eksctl version 0.54.0
2021-06-30 08:53:19 [ℹ]  using region cn-north-1
2021-06-30 08:53:19 [ℹ]  setting availability zones to [cn-north-1d cn-north-1b cn-north-1a]
2021-06-30 08:53:19 [ℹ]  subnets for cn-north-1d - public:192.168.0.0/19 private:192.168.96.0/19
2021-06-30 08:53:19 [ℹ]  subnets for cn-north-1b - public:192.168.32.0/19 private:192.168.128.0/19
2021-06-30 08:53:19 [ℹ]  subnets for cn-north-1a - public:192.168.64.0/19 private:192.168.160.0/19
2021-06-30 08:53:19 [ℹ]  using Kubernetes version 1.19
2021-06-30 08:53:19 [ℹ]  creating EKS cluster "bjs-test" in "cn-north-1" region with
2021-06-30 08:53:19 [ℹ]  if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=cn-north-1 --cluster=bjs-test'
2021-06-30 08:53:19 [ℹ]  CloudWatch logging will not be enabled for cluster "bjs-test" in "cn-north-1"
2021-06-30 08:53:19 [ℹ]  you can enable it with 'eksctl utils update-cluster-logging --enable-types={SPECIFY-YOUR-LOG-TYPES-HERE (e.g. all)} --region=cn-north-1 --cluster=bjs-test'
2021-06-30 08:53:19 [ℹ]  Kubernetes API endpoint access will use default of {publicAccess=true, privateAccess=false} for cluster "bjs-test" in "cn-north-1"
2021-06-30 08:53:19 [ℹ]  2 sequential tasks: { create cluster control plane "bjs-test", 2 sequential sub-tasks: { wait for control plane to become ready, 1 task: { create addons } } }
2021-06-30 08:53:19 [ℹ]  building cluster stack "eksctl-bjs-test-cluster"
2021-06-30 08:53:19 [ℹ]  deploying stack "eksctl-bjs-test-cluster"
2021-06-30 08:53:49 [ℹ]  waiting for CloudFormation stack "eksctl-bjs-test-cluster"
2021-06-30 08:54:20 [ℹ]  waiting for CloudFormation stack "eksctl-bjs-test-cluster"
2021-06-30 08:55:20 [ℹ]  waiting for CloudFormation stack "eksctl-bjs-test-cluster"
2021-06-30 08:55:20 [✖]  unexpected status "ROLLBACK_IN_PROGRESS" while waiting for CloudFormation stack "eksctl-bjs-test-cluster"
2021-06-30 08:55:20 [ℹ]  fetching stack events in attempt to troubleshoot the root cause of the failure
2021-06-30 08:55:20 [!]  AWS::EC2::InternetGateway/InternetGateway: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::Subnet/SubnetPrivateCNNORTH1B: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::RouteTable/PublicRouteTable: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::RouteTable/PrivateRouteTableCNNORTH1A: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::Subnet/SubnetPrivateCNNORTH1A: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::RouteTable/PrivateRouteTableCNNORTH1B: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::Subnet/SubnetPublicCNNORTH1B: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::RouteTable/PrivateRouteTableCNNORTH1D: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::Subnet/SubnetPrivateCNNORTH1D: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::Subnet/SubnetPublicCNNORTH1A: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::VPCGatewayAttachment/VPCGatewayAttachment: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::SecurityGroup/ClusterSharedNodeSecurityGroup: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::IAM::Role/ServiceRole: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::SecurityGroup/ControlPlaneSecurityGroup: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::IAM::Policy/PolicyELBPermissions: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::NatGateway/NATGateway: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPublicCNNORTH1D: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPublicCNNORTH1B: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPrivateCNNORTH1B: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::SecurityGroupIngress/IngressInterNodeGroupSG: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::IAM::Policy/PolicyCloudWatchMetrics: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPrivateCNNORTH1A: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::Route/PublicSubnetRoute: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPublicCNNORTH1A: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [!]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPrivateCNNORTH1D: DELETE_IN_PROGRESS
2021-06-30 08:55:20 [✖]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPrivateCNNORTH1D: CREATE_FAILED – "Resource creation cancelled"
2021-06-30 08:55:20 [✖]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPublicCNNORTH1A: CREATE_FAILED – "Resource creation cancelled"
2021-06-30 08:55:20 [✖]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPublicCNNORTH1D: CREATE_FAILED – "Resource creation cancelled"
2021-06-30 08:55:20 [✖]  AWS::EC2::NatGateway/NATGateway: CREATE_FAILED – "Resource creation cancelled"
2021-06-30 08:55:20 [✖]  AWS::EC2::Route/PublicSubnetRoute: CREATE_FAILED – "Resource creation cancelled"
2021-06-30 08:55:20 [✖]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPrivateCNNORTH1A: CREATE_FAILED – "Resource creation cancelled"
2021-06-30 08:55:20 [✖]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPrivateCNNORTH1B: CREATE_FAILED – "Resource creation cancelled"
2021-06-30 08:55:20 [✖]  AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPublicCNNORTH1B: CREATE_FAILED – "Resource creation cancelled"
2021-06-30 08:55:20 [✖]  AWS::EKS::Cluster/ControlPlane: CREATE_FAILED – "Cannot create cluster 'bjs-test' because cn-north-1d, the targeted availability zone, does not currently have sufficient capacity to support the cluster. Retry and choose from these availability zones: cn-north-1b, cn-north-1a (Service: AmazonEKS; Status Code: 400; Error Code: UnsupportedAvailabilityZoneException; Request ID: bd50d2a9-6877-4ddc-add4-e773d4562a43; Proxy: null)"
2021-06-30 08:55:20 [!]  1 error(s) occurred and cluster hasn't been created properly, you may wish to check CloudFormation console
2021-06-30 08:55:20 [ℹ]  to cleanup resources, run 'eksctl delete cluster --region=cn-north-1 --name=bjs-test'
2021-06-30 08:55:20 [✖]  ResourceNotReady: failed waiting for successful resource state
Error: failed to create cluster "bjs-test"

Anything else we need to know?

Versions

$ eksctl version
0.54.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions