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

Returning 500 instead of 503 when cloud is unavailable #9

Open
netoax opened this issue Mar 25, 2019 · 0 comments
Open

Returning 500 instead of 503 when cloud is unavailable #9

netoax opened this issue Mar 25, 2019 · 0 comments

Comments

@netoax
Copy link
Contributor

netoax commented Mar 25, 2019

The back-end is returning 500 (Internal server error) instead of 503 (Service unavailable) when connection with cloud service times out. The fix should be to include ETIMEDOUT and EAGAIN to the list of request errors, which means the cloud service is unavailable.

Steps to reproduce

  1. Bring WebUI's container up
  2. Bring Cloud's container up
  3. Don't connect them together
  4. Run cloud configuration
  5. Try to sign up

Expected result
Show an error message telling that the cloud service is unavailable.

Actual result
Shows an error message telling that an unexpected error occurred.

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

No branches or pull requests

2 participants