You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've run into a repeat error while attempting to apply a resize to a MongoDB managed database instance using this provider.
Error: Error resizing database cluster: PUT https://api.digitalocean.com/v2/databases/<id>/resize: 422 (request "<id>") error calculating additional storage size: failed to get plan disk range: rpc error: code = InvalidArgument desc = invalid request
For context the error started after attempting to move the database cluster into HA mode by setting node_count integer from 1 to 3. I initially thought it might be because we didn't define storage_size_mib after noticing it was set to 0 in our state, but setting the value to the default size for the slug we are using still returned the same error.
As a workaround we have manually resized the cluster from the DO web portal and reconciled the state.
I'm not quite sure if it's user error on our end (e.g. a missing or incorrect value somewhere) or a bug so I figured I'd run it past the community discussions first for some insight before potentially polluting the reports queue over on the issues tab.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
We've run into a repeat error while attempting to apply a resize to a MongoDB managed database instance using this provider.
Error: Error resizing database cluster: PUT https://api.digitalocean.com/v2/databases/<id>/resize: 422 (request "<id>") error calculating additional storage size: failed to get plan disk range: rpc error: code = InvalidArgument desc = invalid request
For context the error started after attempting to move the database cluster into HA mode by setting
node_count
integer from 1 to 3. I initially thought it might be because we didn't definestorage_size_mib
after noticing it was set to 0 in our state, but setting the value to the default size for the slug we are using still returned the same error.As a workaround we have manually resized the cluster from the DO web portal and reconciled the state.
I'm not quite sure if it's user error on our end (e.g. a missing or incorrect value somewhere) or a bug so I figured I'd run it past the community discussions first for some insight before potentially polluting the reports queue over on the issues tab.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions