You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I was trying to bootsrap a KIT cluster using kitctl CLI and I got the below error message.
` % kitctl bootstrap kitctl-$(whoami)
Bootstrapping "kitctl-xxxxx"
Created role kitctl-xxxxx
Ensured policy kitctl-xxxxx for kitctl-xxxxx
Created vpc vpc-xxxxx
reconciling cluster.Address, err ensuring IP address, allocating address, AddressLimitExceeded: The maximum number of addresses has been reached.
status code: 400, request id: xxxxx
reconciling cluster.InstanceProfile, err attaching role policy RequestCanceled: request context canceled
caused by: context canceled
reconciling cluster.Address, ensuring IP address, allocating address, AddressLimitExceeded: The maximum number of addresses has been reached.
status code: 400, request id: xxxxx; reconciling cluster.InstanceProfile, attaching role policy RequestCanceled: request context canceled
caused by: context canceled
This error message made me think the issue was that with my VPC not having free IP addresses. But that was not the issue since the VPC was just created and had /16 free IPs. The issue was that my AWS account had run out of available Elastic IP addresses (The default quota for the number of avaialble EIPs in an AWS account is 5, and I was already using up all the 5).
My feedback is to provide a more specific error message to help the user quickly narrow down the issue to be the unavailability of Elastic IP addresses in the account.
Thank you!
The text was updated successfully, but these errors were encountered:
Hello, I was trying to bootsrap a KIT cluster using kitctl CLI and I got the below error message.
This error message made me think the issue was that with my VPC not having free IP addresses. But that was not the issue since the VPC was just created and had /16 free IPs. The issue was that my AWS account had run out of available Elastic IP addresses (The default quota for the number of avaialble EIPs in an AWS account is 5, and I was already using up all the 5).
My feedback is to provide a more specific error message to help the user quickly narrow down the issue to be the unavailability of Elastic IP addresses in the account.
Thank you!
The text was updated successfully, but these errors were encountered: