Instances may be terminated during deploy-code

[jamesiarmes]

Issue by pdrakeweb
Tuesday Nov 24, 2015 at 21:49 GMT
Originally opened as https://github.com/acquia/cloud-moonshot/issues/53

---

Instances may be terminated during deploy-code if the health checks fail. This may result in the instance being terminated/relaunched by the ASG. Suspending the Terminate and ReplaceUnhealthy processes on the ASG seems to help, unless the instance is being de-registered/registered with the ELB during the deployment process. When this occurs, instances are still being terminated leading me to believe that registration is either resetting the ASG scaling processes or some other mechanism is at work.

Worse still is that when a code deploy deployment is in-process and the instance it is deploying to terminates, it may hang for 1hr. This means when a new instance is started, code cannot be deployed to it unless the original deployment is terminated via CLI or console.

[jamesiarmes]

Comment by askreet
Friday Dec 18, 2015 at 17:18 GMT

---

ASGs just added instance protection as a feature, it might be useful for this story.

[nikgregory]

This defect/enhancement explains issues that I occasionally get with launching a dev stack.