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

AWS Autoscaling Group & Launch Configuration ordering error #1648

Closed
johnrengelman opened this issue Apr 23, 2015 · 6 comments
Closed

AWS Autoscaling Group & Launch Configuration ordering error #1648

johnrengelman opened this issue Apr 23, 2015 · 6 comments

Comments

@johnrengelman
Copy link
Contributor

I've been running into problems making changes to an AWS Launch Configuration.
Very similar to #532 and according to 09f5935 I should set create_before_destroy = true.

Setting that lifecycle value allows changes to the Launch Configuration to work, but it prevents setting up a new environment from a clean slate. Since there isn't an existing Launch Configuration, Terraform seems to end up in a cycle dependency.

@phinze
Copy link
Contributor

phinze commented Apr 23, 2015

We're working on making improvements around the cycle detection error messaging, so this is definitely a confusing state to be in right now. But the fact is that you can introduce legitimate cycles when you add create_before_destroy to a resource that has non-CBD dependencies.

If you add CBD to the chain of resources depended on by your launch configuration, does that sort the cycle for you?

@johnrengelman
Copy link
Contributor Author

I had tried that, but it didn't seem to help at the time. Not at a point where I can go back and try it again either.

@phinze
Copy link
Contributor

phinze commented Apr 25, 2015

Setting that lifecycle value allows changes to the Launch Configuration to work, but it prevents setting up a new environment from a clean slate. Since there isn't an existing Launch Configuration, Terraform seems to end up in a cycle dependency.

@johnrengelman having trouble coming up with a repro case here, do you think you might be able to give an example of the configs you're working with when you encounter this problem?

@johnrengelman
Copy link
Contributor Author

The sample here: #1637 (comment) is what was doing it for me.

Having the create_before_destroy only worked if the LC was already existing. When it was deleted, I couldn't create a brand new one.

@mitchellh
Copy link
Contributor

I'm going to say this is fixed or a dup of #1109 depending on what it is describing? If not, please let me know.

@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