pulumi-eks icon indicating copy to clipboard operation
pulumi-eks copied to clipboard

pulumi up eks failed

Open Matrix-Zhang opened this issue 2 years ago • 2 comments

What happened?

aws:ec2:LaunchConfiguration (relation-nodeLaunchConfiguration):
    error: deleting urn:pulumi:dev::relation-eks::eks:index:Cluster$aws:ec2/launchConfiguration:LaunchConfiguration::relation-nodeLaunchConfiguration: 1 error occurred:
        * error deleting Autoscaling Launch Configuration (relation-nodeLaunchConfiguration-21fee55): ResourceInUse: Cannot delete launch configuration relation-nodeLaunchConfiguration-21fee55 because it is attached to AutoScalingGroup relation-ca6bb7ef-NodeGroup-13EZ6SN1RIE5X
        status code: 400, request id: 0ac0a61d-bb63-41e3-ae45-b70d11eef508
 
  pulumi:pulumi:Stack (relation-eks-dev):
    error: update failed

Steps to reproduce

change eksCluster's node minSize || maxSize

Expected Behavior

pulumi up ok

Actual Behavior

pulumi up failed

Versions used

0.37.1

Matrix-Zhang avatar Apr 25 '22 08:04 Matrix-Zhang

Potential dupe of: #178

KrisJohnstone avatar May 18 '22 08:05 KrisJohnstone

I tried to modify the cluster by adding extraNodeSecurityGroups and it produced the same kind of error

  aws:ec2:LaunchConfiguration (beacon-dev-nodeLaunchConfiguration):
    error: deleting urn:pulumi:beacon.dev::beacon-infra::ssa-pulumi:module:EKS$eks:index:Cluster$aws:ec2/launchConfiguration:LaunchConfiguration::beacon-dev-nodeLaunchConfiguration: 1 error occurred:
    	* error deleting Autoscaling Launch Configuration (beacon-dev-nodeLaunchConfiguration-196ef78): ResourceInUse: Cannot delete launch configuration beacon-dev-nodeLaunchConfiguration-196ef78 because it is attached to AutoScalingGroup beacon-dev-708d6978-NodeGroup-1QHWU3F1B8FXY
    	status code: 400, request id: eedb72ad-5d04-49ab-ab25-88b68a0e80e8

samirpatel-slingshot avatar May 20 '22 20:05 samirpatel-slingshot