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

Skip empty ECS clusters instead of failing entire backend #2168

Closed
ghost opened this issue Sep 22, 2017 · 2 comments
Closed

Skip empty ECS clusters instead of failing entire backend #2168

ghost opened this issue Sep 22, 2017 · 2 comments
Labels
area/provider/ecs kind/bug/possible a possible bug that needs analysis before it is confirmed or fixed. status/5-frozen-due-to-age
Milestone

Comments

@ghost
Copy link

ghost commented Sep 22, 2017

Do you want to request a feature or report a bug?

bug

What did you do?

I tried to use new ECS backend feature - autoDiscoverClusters.
So I added to my command line option ecs.autodiscoverclusters=true

It generally works, but with one remark.

I had one cluster without instances.
Until I removed it, ecs backend wasnt working at all, giving me this error

"time="2017-09-22T19:01:33Z" level=error msg="Provider connection error InvalidParameterException: Container instance cannot be empty."

There wasn't even an ECS tab in traefik UI.
I believe this is a wrong behaviour, you should just skip empty clusters, not bring down whole backend.

Output of traefik version: (What version of Traefik are you using?)

1.4rc3
@jeffreykoetsier
Copy link
Contributor

PR #2170

@ldez ldez added kind/bug/possible a possible bug that needs analysis before it is confirmed or fixed. and removed status/0-needs-triage labels Sep 23, 2017
@traefiker
Copy link
Contributor

Closed by #2170.

@traefiker traefiker added this to the 1.4 milestone Sep 29, 2017
@traefik traefik locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/provider/ecs kind/bug/possible a possible bug that needs analysis before it is confirmed or fixed. status/5-frozen-due-to-age
Projects
None yet
Development

No branches or pull requests

3 participants