Skip to content

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

@malaskowski

Description

@malaskowski

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.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions