"Attribute 'Arn' does not exist" error on the controlPlane resource during the stack creation

[laurentdroin]

Attempting to create an EKS cluster with eksctl 0.179.0 fails.

It fails during the stack creation:

2024-06-03 10:11:28 [✖]  unexpected status "CREATE_FAILED" while waiting for CloudFormation stack "eksctl-ldr-test-eksctl-june-3-cluster"
2024-06-03 10:11:28 [✖]  unexpected status "CREATE_FAILED" while waiting for CloudFormation stack "eksctl-ldr-test-eksctl-june-3-cluster"
2024-06-03 10:11:28 [ℹ]  fetching stack events in attempt to troubleshoot the root cause of the failure
2024-06-03 10:11:28 [✖]  AWS::CloudFormation::Stack/eksctl-ldr-test-eksctl-june-3-cluster: CREATE_FAILED – "The following resource(s) failed to create: [ControlPlane]. "
2024-06-03 10:11:28 [✖]  AWS::EKS::Cluster/ControlPlane: CREATE_FAILED – "Attribute 'Arn' does not exist"
2024-06-03 10:11:28 [!]  1 error(s) occurred and cluster hasn't been created properly, you may wish to check CloudFormation console
2024-06-03 10:11:28 [ℹ]  to cleanup resources, run 'eksctl delete cluster --region=us-east-1 --name=ldr-test-eksctl-june-3'
2024-06-03 10:11:28 [✖]  ResourceNotReady: failed waiting for successful resource state

This seems to be a timing issue because if the eksctl command is run with the '--cfn-disable-rollback' flag to prevent the stack rollback, I can see that even thought the stack creation failed, the role "ServiceRole" is properly created and the ARN is available. As a matter of fact, if I "retry" the stack, it completes and creates fine.

[github-actions]

Hello laurentdroin 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

[cPu1]

@laurentdroin, can you share your ClusterConfig file or CLI args used to create the cluster? Are you able to consistently reproduce this?

[laurentdroin]

@cPu1 - Yes, I can reproduce consistently. Here is the command I used yesterday (I obfuscated the IDs of the private subnet and my email address):

eksctl create cluster --name ldr-test-eksctl-june-3 --region us-east-1 --version 1.29 --vpc-private-subnets subnet-XXX,subnet-XXX --tags Owner=me@address.com,blah=bleh --node-type t3.xlarge -N 3 --node-volume-size 20 --instance-prefix ldr-eksctl-june-3-

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[laurentdroin]

Commenting in order to remove the stale label.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[edmonl]

I got this too with eksctl 0.188. Not sure if it's relevant, that I updated IAM permissions to the latest Minimum Permissions on the doc site before trying eksctl 0.188.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[cPu1]

I got this too with eksctl 0.188. Not sure if it's relevant, that I updated IAM permissions to the latest Minimum Permissions on the doc site before trying eksctl 0.188.

@edmonl, can you share your ClusterConfig file and the output from running the command?