-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting Pause cluster to true raises error #47
Comments
Looks like the MongoDB Atlas API returned a 409 because the cluster is paused. You might have to file a ticket with Mongo Support about this maybe? |
Hi Akshay, Just to clarify, the cluster was in a running state and this was an attempt to set pause to true. Ive found that the same issue happens if you try to set a paused cluster to running. This issue only happens if using the provider. Doing the same actions via the API works fine. Thanks |
Thanks for that clarification @dbamohsin. Could you please share the API endpoints and payload you used to update your cluster? Also, attaching the terraform file and the state file would help me reproduce the error locally. |
Hi Akshay. Here is some detail around the issue. mongodb-atlas.tf - creating the cluster works fine (with paused set to false)
when attempting to set the cluster state to paused by changing the paused to true:
Produces the following plan:
and produces the following error on apply:
Replicating this in the API:The following API call works successfully to set the cluster state to paused:
Payload (sanitised):
|
HI Akshay, has this been verified? it still causes us problems when pausing clusters. Thanks Mohsin |
Hey @dbamohsin I still haven't had time to verify this. But in the api payload you've sent, you set the |
Hi Akshay, Good spot, the API payload should have been
Payload output:
I have tested both ways via the API and it works as it should. |
Hi,
When making a change to set a cluster resource to paused, the following error is received and the plan is not applied.
The text was updated successfully, but these errors were encountered: