-
Notifications
You must be signed in to change notification settings - Fork 261
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
EC2 Controller sometimes doesn't delete the instance after the resource is deleted #2026
Comments
I don't use ArgoCD. I don't feel these two issues are related. The error logs are different. The delete log of 'example-service-81aa88bbb8-ec2-instance' is non-existent. All traces of that instance are lost from the Kubernetes cluster while it is running without anything controlling it. |
@a-hilaly It's always the same error.
It doesn't look like a 'delete' event issue. These error logs are generated even before that. I also noticed that instances that would not terminate wouldn't print an Instance ID if I tried 'kubectl get instances'. In contrast, the other instances have the Instance ID in place. |
Issues go stale after 180d of inactivity. |
Stale issues rot after 60d of inactivity. |
Rotten issues close after 60d of inactivity. |
@ack-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
@a-hilaly: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Rotten issues close after 60d of inactivity. |
@ack-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Describe the bug
I see this issue where the EC2 controller doesn't delete an EC2 even after the resource is deleted.
A parent resource of mine adopts the
Instance
resources here, and the deletion is cascaded from the parent resource. The first resource in the logs was created and deleted successfully and had the same manifest template. I also verified thatmonitoring
is enabled in the resource manifest.If I run
kubectl get instances
, I don't see this instance anymore, but I can see it in my AWS console.The logs(Some texts have been redacted).
Steps to reproduce
It is reproducible only some of the time. It happens randomly with random instances.
Expected outcome
The EC2 should be deleted once the resource is deleted.
Environment
The text was updated successfully, but these errors were encountered: