Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Invalid IAM Instance Profile name when creating ASG #8039

Open
inesshz opened this issue Nov 22, 2024 · 1 comment
Open

[Bug] Invalid IAM Instance Profile name when creating ASG #8039

inesshz opened this issue Nov 22, 2024 · 1 comment
Labels

Comments

@inesshz
Copy link

inesshz commented Nov 22, 2024

What were you trying to accomplish?

We use eksctl to create managed Nodegroups for our cluster.

What happened?

We noticed the following error when checking cloudtrail for the CreateAutoScalingGroup API call (08:13:09 (UTC+00:00)):

"You must use a valid fully-formed launch template. Value (eks-88c9a977-44e8-7220-1bc8-dbbca45af78b) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name"

The API call for the createInstanceProfile was successful at 08:13:06 (UTC+00:00).

The CreateAutoScalingGroup API call will retry after few seconds and it will work successfully at 08:13:40 (UTC+00:00)

However, in some of our clusters, the CreateAutoScalingGroup API call did not retry and ASG was not created.
This happens randomly in some of the clusters and its hard to replicate.

Logs

There are no specific logs to mention, the only thing we could see from cloudtrail is that the createAutoscalingGroup API call was not retried and the ASG was not created for some of the clusters.
The solution was that we deleted the Nodegroup cloudformation and re-created it again, and this time it worked.

Anything else we need to know?

We did reach out to AWS support and they mentioned that at the AMI side there is a propagation delay and that the two API calls had only few seconds difference.
They suggested to add a delay between these API calls.

Please let us know how this can be done or if this can be fixed?

Versions

$ eksctl info

v0.183.0

Copy link
Contributor

Hello inesshz 👋 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant