Closed nicelyc closed 7 years ago
This was due to a target group that did not have any ALB listeners (and therefore no health checks) associated with it.
@nicelyc I am having the same issue, could you add example how you solved it?
I have found out that my problem was with wrong Health check configuration. I've verified the health check manually on ec2 instance and it was not working as expected.
I'm having the same prob...oh never mind fixed it like the others did
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.
Terraform Version
v0.7.13
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/nicelyc/5d0ece28477116ecae8299d27bb19e96
Panic Output
n/a
Expected Behavior
Autoscaling group creation should have completed after number of healthy instances reached minimum ELB capacity. This appears to be a regression, and was functional in 0.7.4.
Actual Behavior
Autoscaling group creation timed out and reported zero healthy instances in the ELB, despite the fact that ELB shows two healthy instances.
(note: the third failed instance is expected, since we only have two tasks running)
Steps to Reproduce
terraform apply
(note, config above is partial)Important Factoids
Autoscaling instances are ECS container instances. Health checks call exposed port on container instances. Tasks were running and responding on two of three instances.
References
n/a