You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I upgrade release from 1.1.0 to 1.3.0 and add some changes to launch configuration, such as key name,
I'm submitting a...
bug report
What is the current behavior?
* aws_launch_configuration.workers (deposed #0): ResourceInUse: Cannot delete launch configuration project-prod-020180630105107074900000001 because it is attached to AutoScalingGroup project-prod-monitoring
status code: 400, request id: 46f32656-8661-11e8-9e77-51ef4818b760
If this is a bug, how to reproduce? Please include a code sample if relevvant.
change ami image id, add/remove key pair name, or other which need re-create a new launch configuration.
What's the expected behavior?
Smoothly updated.
Are you able to fix this problem and submit a PR? Link here if you have already.
I am still investigating this issue, if I can fix, will raise PR.
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.
I have issues
Recently I upgrade release from 1.1.0 to 1.3.0 and add some changes to launch configuration, such as key name,
I'm submitting a...
What is the current behavior?
If this is a bug, how to reproduce? Please include a code sample if relevvant.
change ami image id, add/remove key pair name, or other which need re-create a new launch configuration.
What's the expected behavior?
Smoothly updated.
Are you able to fix this problem and submit a PR? Link here if you have already.
I am still investigating this issue, if I can fix, will raise PR.
Environment details
Any other relevant info
Here is the fix someone mentioned:
hashicorp/terraform#532 (comment)
The text was updated successfully, but these errors were encountered: