-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Unknown
-
None
-
Component/s: Astrolabe, Atlas Testing
-
None
-
Not Needed
Summary
The cloud-qa Atlas instance is returning CLUSTER_ALREADY_REQUESTED_DELETION errors. For example:
[2024/12/02 00:33:38.809] WARNING:astrolabe.commands:400: Bad Request. Error Code: 'CLUSTER_ALREADY_REQUESTED_DELETION': The cluster f9da831e48 has already been requested for deletion. (DELETE https://cloud-qa.mongodb.com/api/atlas/v1.0/groups/674d4f7fdb24e71a7b8fc04d/clusters/f9da831e48)
See here for the full log.
Motivation
Who is the affected end user?
Who are the stakeholders?
How does this affect the end user?
Are they blocked? Are they annoyed? Are they confused?
How likely is it that this problem or use case will occur?
Main path? Edge case?
If the problem does occur, what are the consequences and how severe are they?
Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?
Is this issue urgent?
Does this ticket have a required timeline? What is it?
Is this ticket required by a downstream team?
Needed by e.g. Atlas, Shell, Compass?
Is this ticket only for tests?
Does this ticket have any functional impact, or is it just test improvements?
Acceptance Criteria
What specific requirements must be met to consider the design phase complete?
- related to
-
DRIVERS-2749 [Astrolabe] Investigate using Local Deployments from the Atlas CLI
-
- Backlog
-