[DRIVERS-2723] Atlas cluster setup generating duplicate cluster names Created: 14/Sep/23  Updated: 15/Sep/23

Status: Implementing
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Bug Priority: Unknown
Reporter: Bailey Pearson Assignee: Bailey Pearson
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to CSHARP-4788 Atlas cluster setup generating duplic... Backlog
split to CDRIVER-4723 Atlas cluster setup generating duplic... Closed
split to CXX-2755 Atlas cluster setup generating duplic... Closed
split to GODRIVER-2983 Atlas cluster setup generating duplic... Closed
split to MOTOR-1189 Atlas cluster setup generating duplic... Closed
split to NODE-5635 Atlas cluster setup generating duplic... Closed
split to PHPLIB-1239 Atlas cluster setup generating duplic... Closed
split to PYTHON-3960 Atlas cluster setup generating duplic... Closed
split to RUBY-3328 Atlas cluster setup generating duplic... Closed
split to RUST-1762 Atlas cluster setup generating duplic... Closed
split to JAVA-5165 Atlas cluster setup generating duplic... Backlog
Driver Changes: Needed - No Spec Changes
Downstream Changes Summary:

Drivers MUST pass the evergreen expansion `execution` to setup-atlas-cluster.sh and teardown-atlas-cluster.sh in drivers-evergreen-tools.

Drivers that use `include_expansions_in_env` or `add_expansions_to_env` or already provide the `execution` expansion when calling these scripts do not require changes.

Start date:
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4723 Won't Do
CXX-2755 Works as Designed
CSHARP-4788 Backlog
GODRIVER-2983 Works as Designed
JAVA-5165 Backlog
NODE-5635 Done
MOTOR-1189 Duplicate
PYTHON-3960 Works as Designed
PHPLIB-1239 Works as Designed
RUBY-3328 Fixed 2.19.1
RUST-1762 Works as Designed

 Description   

Summary

The changes made in DRIVERS-2710 did not make atlas clusters generated by the tooling sufficiently unique.  The scripts should be updated to ensure that there are no conflicts in Atlas clusters generated by CI tooling.

Motivation

Who is the affected end user?

drivers engineers.

How does this affect the end user?

Drivers may be seeing failures in CI for tests that set up Atlas clusters.

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 at failures in CI.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes.

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?



 Comments   
Comment by Githook User [ 15/Sep/23 ]

Author:

{'name': 'Bailey Pearson', 'email': 'bailey.pearson@gmail.com', 'username': 'baileympearson'}

Message: DRIVERS-2723: ensure atlas cluster names are unique (#351)
Branch: master
https://github.com/mongodb-labs/drivers-evergreen-tools/commit/1f018c7a248c4fcda6cb7a77043fd673755e0986

Generated at Thu Feb 08 08:26:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.