-
Type: Bug
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Component/s: None
-
None
-
Needed
-
Summary
drivers-evergreen-tools' setup-atlas-cluster.sh creates a unique cluster per-commit but not per invocation. This can lead to race conditions for drivers that have implemented both the search index management API and the FAAS failover testing where the CI tasks setup / teardown a cluster with the same name within the same CI run. We should add a unique identifier (a task id, a random number, ect) to the provisioned cluster's name so CI tasks do not interfere with each other.
Motivation
Who is the affected end user?
drivers engineers.
How does this affect the end user?
Drivers may see flaky FAAS failover tests and search index tests.
How likely is it that this problem or use case will occur?
likely.
If the problem does occur, what are the consequences and how severe are they?
minor annoyance.
Is this issue urgent?
This ticket should be done soon so that as more drivers implement the new CI tasks, they are not adding flaky tests into their CI and so that drivers who currently have this can fix their flaky tests.
Is this ticket required by a downstream team?
no.
Is this ticket only for tests?
yes.
Acceptance Criteria
Update setup-atlas-cluster to create a unique cluster name per-invocation instead of a unique name per-commit.
- split to
-
CSHARP-4777 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Backlog
-
CXX-2743 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Backlog
-
CDRIVER-4714 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Closed
-
GODRIVER-2969 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Closed
-
MOTOR-1185 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Closed
-
NODE-5601 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Closed
-
PYTHON-3944 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Closed
-
RUBY-3324 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Closed
-
RUST-1755 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Closed
-
PHPLIB-1226 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Closed
-
JAVA-5130 Atlas cluster setup script should create a unique cluster per-invocation, not per commit
- Closed