Comments (5)
Hey there
I noticed you're trying to deploy server version 7.0.1
. MongoDB deployment with server version >= 7.0 is currently not supported by the community operator. We are working on adding this support to the community operator soon.
from mongodb-kubernetes-operator.
I have also tried with 6.0.5 as the documentation suggests but get the same error. This Event
is from the MongoDB pod.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 22m default-scheduler Successfully assigned mongodb/mongodb-dev-0 to k8s-virtual-6
Normal Pulling 22m kubelet Pulling image "quay.io/mongodb/mongodb-kubernetes-operator-version-upgrade-post-start-hook:1.0.7"
Normal Pulled 22m kubelet Successfully pulled image "quay.io/mongodb/mongodb-kubernetes-operator-version-upgrade-post-start-hook:1.0.7" in 524ms (524ms including waiting)
Normal Started 22m kubelet Started container mongodb-agent-readinessprobe
Normal Started 22m kubelet Started container mongod-posthook
Normal Pulling 22m kubelet Pulling image "quay.io/mongodb/mongodb-kubernetes-readinessprobe:1.0.15"
Normal Pulled 22m kubelet Successfully pulled image "quay.io/mongodb/mongodb-kubernetes-readinessprobe:1.0.15" in 473ms (473ms including waiting)
Normal Created 22m kubelet Created container mongodb-agent-readinessprobe
Normal Created 22m kubelet Created container mongod-posthook
Normal Pulled 22m kubelet Successfully pulled image "quay.io/mongodb/mongodb-agent:12.0.25.7724-1" in 463ms (463ms including waiting)
Normal Pulling 22m kubelet Pulling image "quay.io/mongodb/mongodb-agent:12.0.25.7724-1"
Normal Created 22m kubelet Created container mongodb-agent
Normal Started 22m kubelet Started container mongodb-agent
Normal Created 22m (x2 over 22m) kubelet Created container mongod
Normal Started 22m (x2 over 22m) kubelet Started container mongod
Normal Pulled 22m (x2 over 22m) kubelet Container image "docker.io/mongodb/mongodb-community-server:6.0.5-ubi8" already present on machine
Warning Unhealthy 22m (x3 over 22m) kubelet Readiness probe failed: panic: open /var/log/mongodb-mms-automation/healthstatus/agent-health-status.json: no such file or directory
goroutine 1 [running]:
main.main()
/workspace/cmd/readiness/main.go:226 +0x19a
Warning Unhealthy 22m (x2 over 22m) kubelet Readiness probe failed:
Warning BackOff 2m45s (x90 over 22m) kubelet Back-off restarting failed container mongod in pod mongodb-dev-0_mongodb(8642484c-7be7-413b-ac77-d5e9189a9f57)
from mongodb-kubernetes-operator.
It's working with operator version v0.7.6
and mongodb version 4.2.6
It's not working with operator version v0.8.2
and mongodb version 4.2.6
.
It's not working with operator version v0.7.6
and mongodb version 6.0.5
.
from mongodb-kubernetes-operator.
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.
from mongodb-kubernetes-operator.
Related Issues (20)
- Connectivity and Authentication Issues with MongoDB Community Operator (v0.8.2) in ReplicaSet Configuration HOT 2
- The deployed mongodb cluster is not working HOT 6
- Mongo v7 with 6.0 compatability fails to start; does not move from Pending phase HOT 7
- Replica set does not start, stuck in phase: Pending HOT 11
- Support for opt-in cleanup of PVCs HOT 6
- Server startup warnings HOT 3
- Nonsecure prometheus HOT 2
- In the quay.io repository, there is no image of the arm architecture. HOT 8
- Create connectionString secret at another namespace
- Support for different resource request / limit for arbiters HOT 1
- can not set setParameter.authenticationMechanisms to SCRAM-SHA-1 HOT 3
- Mongodb-agent is never ready - HOT 7
- Readiness probe failed: command "/opt/scripts/readinessprobe" timed out on DB Pod when installing on Mac M1, even when using arm64 images HOT 9
- Mongodb Operator v0.8.3 crash on aarch64 k8s workers HOT 1
- Current mongo db members is 0 though >0 configured and running HOT 6
- Logging solely to stdout/stderr at the specified log level HOT 9
- It is not possible to pass unique labels and selectors on arbiter and mongo members. HOT 4
- Is it possible to pass resources limits and requests on initContainers? HOT 2
- ReplicaSet stuck in Pending phase via MongoDB Community Operator HOT 25
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mongodb-kubernetes-operator.