-
Notifications
You must be signed in to change notification settings - Fork 162
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
Failed (before master node created) to create EKS cluster fails deletion at first try, succeeds on second #3316
Labels
Comments
pregnor
added
kind/bug
Something isn't working
cloud/aws
area/cluster
distribution/eks
Amazon EKS
labels
Nov 16, 2020
pregnor
changed the title
Failed (before control plane) to create EKS cluster fails deletion at first try, succeeds on second.
Failed (before control plane) to create EKS cluster fails deletion at first try, succeeds on second
Nov 16, 2020
pregnor
changed the title
Failed (before control plane) to create EKS cluster fails deletion at first try, succeeds on second
Failed (before master node created) to create EKS cluster fails deletion at first try, succeeds on second
Mar 18, 2021
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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:
The text was updated successfully, but these errors were encountered: