microsoft / microsoft/AzureTRE
Cosmos containers are not created - API up before Cosmos - 500 error
Open
Nobody has claimed this yet.
bug
has workaround
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
On some deployments it seems that the Cosmos containers are not created. This is likely because the API comes up before Cosmos.
Workaround is to restart the API web ap and the containers are created.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Reproduce a deployment where the API starts before Cosmos, then trace the startup and container-creation path; done means the containers are created without manually restarting the API and the original 500 no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- backend, cloud, database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100