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
Because of a known error in Elastic Beanstalk, blue/green terminate inactive can fail. The problem lies in a timing problem between ec2 resources and eb termination. Sometimes (often for those of use who do continuous deployment) the stack will fail to terminate because it thinks there is still a dependent resource on a security group. In all cases, I have found that requesting that the environment be terminated again after the error results in a successful termination. Since we use eb_deployer so heavily in our continuous delivery scheme, it would be of great value to have a retry termination feature available when the stack fails to terminate initially. It would be valuable to have a number of retry attempts.
The text was updated successfully, but these errors were encountered:
Because of a known error in Elastic Beanstalk, blue/green terminate inactive can fail. The problem lies in a timing problem between ec2 resources and eb termination. Sometimes (often for those of use who do continuous deployment) the stack will fail to terminate because it thinks there is still a dependent resource on a security group. In all cases, I have found that requesting that the environment be terminated again after the error results in a successful termination. Since we use eb_deployer so heavily in our continuous delivery scheme, it would be of great value to have a retry termination feature available when the stack fails to terminate initially. It would be valuable to have a number of retry attempts.
The text was updated successfully, but these errors were encountered: