Launch configurations are not cleaned up

[danieltwagner]

As I create new auto scaling groups in my cluster, I delete the old ASGs. However, the launch configurations that are generated for each ASG are not deleted. Seeing as they are not reused, it would seem appropriate for them to be deleted when the ASG has disappeared. Otherwise creating new ASGs will eventually fail with the following error:

Create Launch Configuration 'www-r01-v010-20130721192302' with image 'ami-xxxxxxxx'
2013-07-21_19:23:04 Exception: LimitExceededException: Status Code: 400, AWS Service: AmazonAutoScaling, AWS Request ID: [id], AWS Error Code: LimitExceeded, AWS Error Message: Launch Configuration limit exceeded - You may only have 100 launch configurations

Maybe I'm using Asgard incorrectly, if so please do let me know.

[claymccoy]

Asgard removes old launch configurations during an ASG deletion. It doesn't remove the current launch configuration. That seems odd to me and I will investigate the reasoning behind it. It sounds like you are at a point where you should investigate Janitor Monkey. https://github.com/Netflix/SimianArmy/wiki/Janitor-Home

[romankor]

Is there anything new to this , its pretty annoying to realized that the build fails every few days because of this

[amoffat]

+1

[bobtfish]

+1

[ajmath]

+1

[dziemid]

+1

[rhussmann]

+1

[brendangibat]

+1

[atkins]

+1

[zshenker]

Any update on this @claymccoy it does not appear that the Launch Configuration is being deleted by Asgard when deleting an Auto Scaling Group?

[OskarKjellin]

+1 Running into this all the time

[steder]

+1, anyone got a workaround for cleaning these up?

[steder]

I just wrote this cleanup script to help out in the interim. Sharing here just in case it ends up being helpful to others. I've exhaustively tested :smile: so if it breaks you get to keep both pieces.

https://gist.github.com/steder/1fddeab0d96f0c8c7bcc

[bobtfish]

Ask amazon for more, by several orders of magnitude (is our solution currently) :)

[sommestad]

+1

[danveloper]

this seems like it would be a fairly simple pull request for somebody to put together and another person to vet... we don't have any team resources dedicated to enhancing Asgard, but if somebody from the community wanted to champion this effort, i'd happily merge it.

If not: what Clay said earlier though -- the alternative is to use Janitor Monkey.

[claudiu-coman]

+1

[haavardw]

+1

[danveloper]

Asgard is no longer being supported. Spinnaker is the new continuous delivery utility from Netflix. It fits on top of existing Asgard structure, though, so it should be a drop-in replacement for those of you using Asgard today => http://spinnaker.io/