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

CFN stack left in DELETE_FAILED state for MNG cluster #195

Closed
couralex6 opened this issue Jan 23, 2021 · 0 comments · Fixed by #196
Closed

CFN stack left in DELETE_FAILED state for MNG cluster #195

couralex6 opened this issue Jan 23, 2021 · 0 comments · Fixed by #196

Comments

@couralex6
Copy link

CFN stacks are occasionally left in DELETE_FAILED state, which is causing our CNI CI tests to fail:

Nodegroup cni-test-8287-mng-for-cni failed to stabilize: [{Code: Ec2SecurityGroupDeletionFailure,Message: DependencyViolation - resource has a dependent object,ResourceIds: [sg-01aca506d267ae11a]}]

Looking at the aws-k8s-tester log, it seems like the first try to delete MNG fails:

2021-01-22T23:22:56.4117354Z {"level":"info","ts":"2021-01-22T23:22:56.411Z","caller":"eks/eks.go:1423","msg":"failed Down","error":"MNGs["cni-test-8287-mng-for-cni"] failed to delete failed to delete stack (previous status reason "The following resource(s) failed to delete: [MNG]. ", current stack status "DELETE_FAILED", current status reason "The following resource(s) failed to delete: [MNG]. ")","started":"18 minutes ago"}

However, when querying directly with EKS API, the MNG was deleted. Deleting the stack manually works.

This does not happen on every run.

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

Successfully merging a pull request may close this issue.

1 participant