Skip to content
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

Error when change is made to aws_launch_configuration #2385

Closed
pfordahl opened this issue Jun 17, 2015 · 4 comments
Closed

Error when change is made to aws_launch_configuration #2385

pfordahl opened this issue Jun 17, 2015 · 4 comments

Comments

@pfordahl
Copy link

Your stack is build and you make a change to the aws_launch_configuration and you apply the change then the error comes up.

  • ResourceInUse: Cannot delete launch configuration terraform-wei3injw2fdc3adjvzzlpeoz74 because it is attached to AutoScalingGroup XXXXX-test
    status code: 400, request id: [962be820-151e-11e5-8088-a1efb38c16d6]
    Error applying plan:

2 error(s) occurred:

  • 1 error(s) occurred:
  • 1 error(s) occurred:
  • ResourceInUse: Cannot delete launch configuration terraform-wei3injw2fdc3adjvzzlpeoz74 because it is attached to AutoScalingGroup XXXXX-test
    status code: 400, request id: [962be820-151e-11e5-8088-a1efb38c16d6]
  • 1 error(s) occurred:
  • aws_autoscaling_group.XXXX: diffs didn't match during apply. This is a bug with Terraform and should be reported.

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

@pfordahl pfordahl changed the title Change to aws_launch_configuration Error when change is made to aws_launch_configuration Jun 17, 2015
@sheldonh
Copy link

Still a problem as at Terraform v0.6.0-dev (ce8baea).

@sheldonh
Copy link

Duplicate of #1109.

@mitchellh
Copy link
Contributor

Agreed that this is a dup of #1109

@ghost
Copy link

ghost commented May 1, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants