Summary

The mongosync team is seeing a BF (REP-5613, logs) where mongo-orchestration is running into this 500 error: Could not find a free port,\nclosed ports: set()\n.

It seems like the issue is coming up because we're using the python free threading beta build python3.13t (according to the logs). When I looked at our code base, I couldn't find any specific references to python3.13t so I'm not sure why we're using it instead of python3.13. If this is not the issue, then the problem could be something else in mongo-orchestration.

Motivation

Who is the affected end user?

Mongosync team.

How does this affect the end user?

We're running into a noisy test infra BF.

How likely is it that this problem or use case will occur?

We've seen ~104 BFGs in the past 2 weeks.

If the problem does occur, what are the consequences and how severe are they?

Noisy BF.

Is this issue urgent?

Luckily we have an auto resolution rule for this. So fixing this isn't super urgent. But, we'd still like to look into this.

Is this ticket required by a downstream team?

Fix needed by mongosync team.

Is this ticket only for tests?

just tests.

Acceptance Criteria

Figure out why this issue is occurring. If this is a bug in mongo-orchestration then it'd be nice to fix it.