-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Marathon provider no longer allows for tasks from different apps within the same backend #2709
Comments
Related to #2333 |
@TrevinTeacutter Could you provide your Marathon application descriptor (json) that produces this error ? |
Has any done any investigation of this issue? |
We removed this line in the marathon template in our local fork of 1.5.2 Traefik and this reverted the behavior to that like 1.4.1 but to ensure the issue this was added for is fixed as well there would probably need to be smarter logic to group all apps together by backends defined (if any). |
Closed by #3109. |
Do you want to request a feature or report a bug?
bug
What did you do?
We have the need for new apps to be included within the same backend so that they are added
to the wrr pool of an existing app in order for zero downtime deployments. This was originally
working with Traefik 1.4.0-rc1 and continued to work until 1.4.2. We didn't try to upgrade
until recently and we are pretty sure this template change caused the issue:
02035d4#diff-080894c4c7f765921235ddb2ceb82140
What did you expect to see?
We expect to see multiple tasks belonging to different marathon apps within the same backend.
What did you see instead?
An error due to a backend already being 'configured' within the template
Output of
traefik version
: (What version of Traefik are you using?)1.4.1 (This is the last version that worked for this)
1.4.2 (First version that failed for the use-case)
1.4.6
1.5.0.rc5
What is your environment & configuration (arguments, toml, provider, platform, ...)?
If applicable, please paste the log output in debug mode (
--debug
switch)The text was updated successfully, but these errors were encountered: