-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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] Error: error updating nodegroup stack: exceeded max wait time for StackUpdateComplete waiter #7448
Comments
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. |
Not stale |
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. |
Not stale |
The problem appears to surface when AWS credentials expire while the upgrade is taking place. |
Yes I tried to reproduce this and this log line I've added seems to confirm my theory:
The SDK configures 403 errors as retryable. Edit: there was a "fix" for STS hashicorp/aws-sdk-go-base#362, but here we are using the default retryer eksctl/pkg/cfn/manager/waiters.go Lines 137 to 141 in 76902cd
I'm inclined to just catch the |
What were you trying to accomplish?
eksctl upgrade nodegroup t2-medium-v1-28
What happened?
How to reproduce it?
Simply run
eksctl upgrade nodegroup ...
Logs
Anything else we need to know?
An important note to mention is that this problem is intermittent. Sometimes this happens, most times the nodegroup updates fine.
If I check CloudFormation, it will say
UPDATE_COMPLETE
and even eksctl reports that the nodegroup is updated and active...Meanwhile I'm left with:
waiting for CloudFormation stack "eksctl-backend-staging-nodegroup-t2-medium-v1-28"
OS:
eksctl installed with:
Versions
The text was updated successfully, but these errors were encountered: