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
What did you do to encounter the bug?
Steps to reproduce the behavior:
Start the MongoDB Community Kubernetes Operator using Helm
Attempt to start a ReplicaSet, using a custom storage class for Amazon EFS storage
What did you expect?
The pods in the ReplicaSet to startup.
What happened instead?
The pods do not start, due to the "Failed to start up WiredTiger under any compatibility version" error.
Screenshots
Operator Information
MongoDB Community Kubernetes Operator 0.11.0
5.0.23
Kubernetes Cluster Information
AWS EKS
Additional context
Wondering if this means that Mongo 5.0.23 cannot be deployed using the operator? It's EOL, so that would make sense.
❯ k get pods
NAME READY STATUS RESTARTS AGE
mongodb-kubernetes-operator-558d9545b8-l7jtz 1/1 Running 0 39m
test-mongodb-0 0/2 Error 12 37m
❯ k get mdbc
NAME PHASE VERSION
test-mongodb
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.
What did you do to encounter the bug?
Steps to reproduce the behavior:
What did you expect?
The pods in the ReplicaSet to startup.
What happened instead?
The pods do not start, due to the "Failed to start up WiredTiger under any compatibility version" error.
Screenshots
Operator Information
Kubernetes Cluster Information
Additional context
Wondering if this means that Mongo 5.0.23 cannot be deployed using the operator? It's EOL, so that would make sense.
The text was updated successfully, but these errors were encountered: