You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm playing around with cdk deploy and cdk destroy to test the DNS name feature I requested in #68
The "cdk destroy" operation takes ages until it finally fails. I'm not 100% sure yet, but it seems as if the spot instance requests issue, you described somewhere in the comments, led to the issue that a second VM has been created, which does not get deleted by the cdk destroy operation and an attempt to delete the whole stack fails because the ENI is still in use by the second spot instance that is running.
and it seems to me that I had no more (or less?) VMs hanging around. There is still the issue with spot instance requests, but at least I could simply "cdk destroy" the whole setup without running into timeouts because of some detached VMs that were not seen by the CDK but blocking the ENI resources so that they could not be deleted.
I'm playing around with cdk deploy and cdk destroy to test the DNS name feature I requested in #68
The "cdk destroy" operation takes ages until it finally fails. I'm not 100% sure yet, but it seems as if the spot instance requests issue, you described somewhere in the comments, led to the issue that a second VM has been created, which does not get deleted by the cdk destroy operation and an attempt to delete the whole stack fails because the ENI is still in use by the second spot instance that is running.
The question is whether there is a way to avoid a second VM to be started, becoming somehow detached from the CDK/CFN state?
The text was updated successfully, but these errors were encountered: