Open pregnor opened 3 years ago
An easier reproduction:
diff --git a/templates/eks/amazon-eks-iam-cf.yaml b/templates/eks/amazon-eks-iam-cf.yaml
index a797c34cd..b6330f938 100644
--- a/templates/eks/amazon-eks-iam-cf.yaml
+++ b/templates/eks/amazon-eks-iam-cf.yaml
@@ -2,6 +2,10 @@ AWSTemplateFormatVersion: '2010-09-09'
Description: 'Amazon EKS IAM'
Parameters:
+ BreakMe:
+ Type: String
+ Description: reproduction requirement.
+
ClusterName:
Type: String
Description: The name of the EKS cluster.
DeleteNodePoolLabelSetActivity is the one that fails to run properly on the first time. The second time this activity does not triggered, so this may be the reason why the second deletion succeed. It is possible that cluster creation fails before node pool label set creations, causing the delete to fail on trying to delete non existing resource.
Describe the bug
When an EKS cluster fails the creation before the control plane successfully being created, the first deletion attempt runs into issues when trying to delete the node pool label set and fails with
secret not found
, but the subsequent deletion attempt succeeds without leaving any resources behind.Steps to reproduce the issue:
secret not found
on node pool stack deletion.Expected behavior
The first deletion attempt should succeed as the second does.
Additional context
My guess is on a non-conditional node pool label set deletion early during the deletion process even when the node pool label set operator had not been installed before.
Error: