Does AMI creation happen even if there is a deploy failure?

[fuzzygroup]

We recently had a spate of weirdness in our deploy stack. The situation we saw was:

• A capistrano deploy happened
• An extra directory in releases appeared beyond the set limit of 3
• We ended up with current pointing one directory behind the last directory in releases
• We ended up with an AMI with things broken (example - the deploy being one release behind)

The best we've been able to figure out is that we had a failed cap deploy.

My suspicion here is that capistrano-asg creates an AMI even if the overall cap deploy fails. Any thoughts?

[sixfeetover]

That's odd, I have not observed that behavior on failed deploys. Do you have the output of the deploy log? It would say the AMI name at the bottom of the log if one was created.