Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Changing the instanceType in an existing NodeGroup results in a 400 failure to delete the LaunchConfig since it is attached to an active ASG

See original GitHub issue

When a NodeGroup is stood up with a given instance type, e.g. t2.medium, and then on a future update is changed to say t3.large, results in the following error:

Diagnostics:
  aws:ec2:LaunchConfiguration (update-existing-nodegroup-ng-2-ondemand-large-nodeLaunchConfiguration):
    error: Plan apply failed: deleting urn:pulumi:dev1::update-existing-nodegroup::eks:index:NodeGroup$aws:ec2/launchConfiguration:LaunchConfiguration::update-existing-nodegroup-ng-2-ondemand-large-nodeLaunchConfiguration: 
    error deleting Autoscaling Launch Configuration (update-existing-nodegroup-ng-2-ondemand-large-nodeLaunchConfiguration-d0932eb):
    ResourceInUse: Cannot delete launch configuration update-existing-nodegroup-ng-2-ondemand-large-nodeLaunchConfiguration-d0932eb because it is attached to AutoScalingGroup update-existing-nodegroup-ng-2-ondemand-large-6410fe15-NodeGroup-1DIVWWS4FCMIU
    status code: 400, request id: f7bfd557-9505-11e9-b696-8ff9971bc5b3

See:

Issue in https://github.com/terraform-providers/terraform-provider-aws/issues/8485
TF work-around, but does not work in pulumi/eks as we do not expose namePrefix as an opt in aws.ec2.LaunchConfiguration
Changing the name of the LaunchConfig resulted in the same error

Manual clean up of the LaunchConfig in the state snapshot and AWS seems to be the only mitigation I’ve found.

cc @jen20 @lukehoban

Issue Analytics

State:
Created 4 years ago
Reactions:5
Comments:21 (6 by maintainers)

Top GitHub Comments

2reactions

tma-unwirecommented, Jun 28, 2022

Are there any recommended work-arounds?

When this happens, I usually go to the parent autoscaling group in the AWS console and change the link to the launch configuration here. And then re-run the Pulumi job with a refesh…

Not so good, but the best I have seen so far.

2reactions

ekahaa-supportcommented, Feb 11, 2022

We have had this issue as well. Any updates please?

Top Results From Across the Web

Delete your Auto Scaling infrastructure - AWS Documentation

When you delete an Auto Scaling group, its desired, minimum, and maximum values are set to 0. As a result, the instances are...

Guide: Updating Instance Type on AWS EKS - Porter Blog

In this guide, we'll walk through an EKS node group update and highlight a few things to look out for when updating an...

aws-sdk | Yarn - Package Manager

Changelog for AWS SDK for JavaScript. 2.1277.0. feature: Appflow: This release updates the ListConnectorEntities API action so that it returns paginated ...

Release 2.6.3-post.62 Onica Group - runway Documentation

Deploy environments are used for selecting the options/variables/parameters to be used with each modules <mod-.

AMS Advanced Change Management User Guide - AWS

For more flexible results when using the CLI, you can use the --query option. ... EC2 instance or auto scaling group For EC2...