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
Got an issue where we ran out of space and it caused pods to crash.
Added some space to the mdb resource and the pods recovered but now I am getting a Failed status for this instance.
Status:
Current Mongo DB Members: 3
Current Stateful Set Replicas: 3
Message: Error deploying MongoDB ReplicaSet: error creating/updating StatefulSet: error creating/updating StatefulSet: StatefulSet.apps "mongodb-dre" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', 'updateStrategy' and 'minReadySeconds' are forbidden
There is nothing to show me exactly what the requested updates are.
Is there anyway to reconcile this without downtime, or recreating the statefulset it's a heavily used MDB instance.
Operator: 0.7.6
MongoDB: 6.0.2
Many thanks.
The text was updated successfully, but these errors were encountered:
we are facing a similar issue on 2 of our mongo-db instances created with the operator. The CRD reports status failed, but the stateful set and the mongodb instances are actually running. However, pushing any changes fail with the same error message. Deleting and recreating the statefulset is a no-go due to this being in production.
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.
Got an issue where we ran out of space and it caused pods to crash.
Added some space to the mdb resource and the pods recovered but now I am getting a
Failed
status for this instance.There is nothing to show me exactly what the requested updates are.
Is there anyway to reconcile this without downtime, or recreating the statefulset it's a heavily used MDB instance.
Operator: 0.7.6
MongoDB: 6.0.2
Many thanks.
The text was updated successfully, but these errors were encountered: