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

Suite status endpoint does not return proper message when DB does not exist #341

Closed
malaskowski opened this issue Aug 29, 2018 · 0 comments · Fixed by #472
Closed

Suite status endpoint does not return proper message when DB does not exist #341

malaskowski opened this issue Aug 29, 2018 · 0 comments · Fixed by #472
Assignees
Labels

Comments

@malaskowski
Copy link
Contributor

Version used

  • AET 2.1.6

Context of the issue/feature

When running new suite and DB for it does not exist and auto creation of DBs is disabled - there is no message what happened but suite run fails.

Steps to reproduce

  1. Make sure that MongoDBClient allowAutoCreate is set to false (disable auto creation of DBs in AET).
  2. Run suite (e.g. using aet.sh) with company and project that does not have DB created.

Result:
Suite is not processed and no progress is presented by suite status endpoint:

{"status":"UNKNOWN","message":""}

From the user (who runs aet.sh) perspective, nothing happens. Internally AET does not process the suite.

Expected:
Suite status endpoint returns proper status (e.g. PROCESSING_ERROR) and message about the problem.

Appendix

This case is already supported by MetadataDAOMongoDBImpl. It looks that this exception is not handled properly.

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

Successfully merging a pull request may close this issue.

2 participants