matrix-org / matrix-org/complement
Homerunner network creation seems to race deployment
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 99
- Forks
- 72
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 8
Description
Encountered an error while processing a homerunner request: 400 {"message":"failed to create deployment: CreateDeployment: Deploy returned error Deploy: Failed to deploy image {Containers:-1 Created:1712588816 ID:sha256:c412da8c2f4203ae5aff3c3dd7097536cbc98ade492e0d91e3be640a73c77951 ....} : Error response from daemon: network complement_homerunner_hookshot_integration_test_1712588803722 not found"}
Seems like something is occasionally racing, subsequent attempts to create a deployment seem to work.
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
Start by reproducing a Homerunner request that creates a deployment and inspect the ordering of network creation and deployment. Use the reported Docker daemon error as the failure condition; done means repeated deployment attempts no longer encounter a missing Homerunner network.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- infrastructure, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100