Describe the bug
Currently when a DB migration fails after a version upgrade, the container start and reports as healthy even if migration fails.
Expected behavior
When a db migration fails, the container should either be marked as unhealthy or completely stopped to indicate a problem to the user. Currently a failed migration only displays an error in the stdout of the docker container, but nowhere else. Stopping the container is important to preserve data integrity. Keeping the container running and seemingly healthy could lead to data loss when a rollback of the DB is required.
Additional context
Instance of such migration failing and not clearly notifying the user, as the interface was usable apart from a single data view.
#4555
Describe the bug
Currently when a DB migration fails after a version upgrade, the container start and reports as healthy even if migration fails.
Expected behavior
When a db migration fails, the container should either be marked as unhealthy or completely stopped to indicate a problem to the user. Currently a failed migration only displays an error in the stdout of the docker container, but nowhere else. Stopping the container is important to preserve data integrity. Keeping the container running and seemingly healthy could lead to data loss when a rollback of the DB is required.
Additional context
Instance of such migration failing and not clearly notifying the user, as the interface was usable apart from a single data view.
#4555