Destroying a freshly deployed cluster stack fails because Tasks are still active

[tillrohrmann]

When trying to destroy a freshly deployed cluster stack, cdk fails with

byoc-demo-cluster-till: destroying... [2/2]
4:56:33 PM | DELETE_IN_PROGRESS   | AWS::EC2::Subnet                          | vpc/PrivateSubnet3/Subnet
4:56:33 PM | DELETE_IN_PROGRESS   | AWS::EC2::Subnet                          | vpc/PrivateSubnet1/Subnet
4:56:33 PM | DELETE_IN_PROGRESS   | AWS::EC2::Subnet                          | vpc/PrivateSubnet2/Subnet
4:56:33 PM | DELETE_IN_PROGRESS   | AWS::EC2::SecurityGroup                   | restate-byoc/security-group
4:56:34 PM | DELETE_FAILED        | AWS::ECS::Cluster                         | restate-byoc/cluster
Resource handler returned message: "Error occurred during operation 'DeleteClusters SDK Error: The Cluster cannot be deleted while Tasks are active. (Service: AmazonECS; Status C
ode: 400; Error Code: ClusterContainsTasksException; Request ID: fd8dc0bb-5f3c-4c3e-961b-ae11c644ece5; Proxy: null)'." (RequestToken: ad9ab3e8-b3d1-3ac7-7931-bdb1602b1500, Handle
rErrorCode: GeneralServiceException)

Is this the intended behavior or should I be able to destroy a byoc stack? If it's the intendend behavior, how would I destroy the stack then?

[pcholakov]

Thanks for this! Not intended, and a known issue I just bumped into yesterday; something I was tracking as a code TODO for now so this is great for visibility. If all else fails, I'll move the above crude fix into the BYOC construct.

[tillrohrmann]

Running npx cdk destroy a second time caused cdk to fail with

byoc-demo-cluster-till: destroying... [2/2]
5:11:39 PM | DELETE_FAILED        | AWS::EC2::Subnet                          | vpc/PrivateSubnet3/Subnet
Resource handler returned message: "The subnet 'subnet-08de2e7fa69609249' has dependencies and cannot be deleted. (Service: Ec2, Status Code: 400, Request ID: 24164869-2f87-4d8b-
ac8e-1977461ae804) (SDK Attempt Count: 1)" (RequestToken: 30d17684-f561-0b75-494d-b3dd330289da, HandlerErrorCode: InvalidRequest)
5:11:39 PM | DELETE_FAILED        | AWS::EC2::Subnet                          | vpc/PrivateSubnet2/Subnet
Resource handler returned message: "The subnet 'subnet-0314835a8681a769f' has dependencies and cannot be deleted. (Service: Ec2, Status Code: 400, Request ID: 32de586a-92c8-408d-
9c84-8bc6de0073be) (SDK Attempt Count: 1)" (RequestToken: f316febf-c388-71d0-2a3e-dc3f5aceeef7, HandlerErrorCode: InvalidRequest)
5:11:39 PM | DELETE_FAILED        | AWS::EC2::Subnet                          | vpc/PrivateSubnet1/Subnet
Resource handler returned message: "The subnet 'subnet-01090e8b9686d63bb' has dependencies and cannot be deleted. (Service: Ec2, Status Code: 400, Request ID: fb3c1c9f-9b9d-49eb-
9ba4-748a3dd541fb) (SDK Attempt Count: 1)" (RequestToken: b26851fb-5824-37fa-1236-bcc912421d24, HandlerErrorCode: InvalidRequest)

[tillrohrmann]

@pcholakov this is the issue I was referring to this morning. Has it been resolved?

[pcholakov]

@tillrohrmann testing it right now, PR inbound!

[pcholakov]

I have some safety concerns about #50 so I'll defer merging this for now; I might hide it behind an opt-in flag if we want to at least get the code in.