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

senza respawn and deployment with Elastigroup blocked by previously failed deployment #558

Open
cjander opened this issue Mar 21, 2019 · 0 comments

Comments

@cjander
Copy link

cjander commented Mar 21, 2019

When in the past a deployment of an Elastigroup failed, the deployment does not reach a final state, it is still running until stopped manually. Due to this a new deploy or respawn will fail with "Can't have 2 Rolls at the same time. Please stop the previous one."

These kind of errors are not handled in or forwarded to the cli, the user just gets "Unknown Error: 400 Client Error" and is clueless about what happened.

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

Successfully merging a pull request may close this issue.

1 participant