Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

L0 ELB created with only one subnet configured #619

Open
davemeyer opened this issue Jun 7, 2018 · 0 comments
Open

L0 ELB created with only one subnet configured #619

davemeyer opened this issue Jun 7, 2018 · 0 comments

Comments

@davemeyer
Copy link

Expected behavior

ELB is generally configured with 3 subnets in 3 AZs

Actual behavior

Only a single subnet in a single AZ was configured

Events as seen from ECS:
The individual tasks were terminating with a SIGTERM: 7 error. That alone didn't tell me much, but the ECS event logs showed the real issue:

(instance i-038db12314955a4d7) is unhealthy in elb l0-chunnelprod0108-Product5c5b5 due to (reason Instance is in the EC2 Availability Zone for which LoadBalancer is not configured to route traffic to.)

Steps to reproduce the behavior

🤷‍♀️ first time i have seen this.

  • V0.10.8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant