-
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] Logs report "failed to acquire semaphore" during deletion #7818
Comments
@artem-nefedov, this is a bug in the logging and concurrency handling but it should not affect normal operation of the command. That part of the codebase is a bit dated and could use some refactoring. We'll look into this soon. |
We also encountered the same error log information when deleting EKS version 1.30, and our eksctl version is 0.183. |
Seeing the same issue with version |
Seeing this issue with eksctl version
|
Test results after finding this and in an attempt to help: 0.176.0 - good until 1.30 - 1.30 is not supported and it refuses to work It'd be great if this could be addressed ASAP and released as 0.189.0 soon. Any chance of that? Pretty bad that it got broken in the first place and even worse that it got left broken for such a long time. Still a better way to manage clusters than Terraform/OpenTofu IMO (when it works properly) (which NO version does for 1.30) |
eksctl version 0.190.0
|
What were you trying to accomplish?
Delete the cluster (it seem to work fine).
What happened?
Logs report this message during deletion:
Deletion still finished without errors, so it does not look like this affect anything. But the log does look like there's a problem.
The behavior is reproduced on all attempts.
How to reproduce it?
Create cluster with 1 managed nodegroup and no unmanaged nodegroups, then delete it.
Versions
The message was not present on eksctl version
0.176.0
with EKS version1.29
(there are no changes in cluster config besides EKS version).The text was updated successfully, but these errors were encountered: