Closed jatinderjawanda closed 2 years ago
Can we set the agent log level to verbose to find a possible reason these files are not being created?
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.
This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information.
I meet the same issue, please reopen it
Hi! I have the same issue, after applying securityContext to containers I am getting this issues: 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:217 +0x19a
Additionally agent complains: cat: /mongodb-automation/agent-api-key/agentApiKey: No such file or directory
Did anybody find a solution?
Hi, I'm also getting the same issue, any workaround or solution so far? Thanks
I hit the same error on macOS on Docker Desktop using Kubernetes, its have working but random stop working and this issue happen!
what i discovered was if i have run a MongoDB in default namespace its give a error, if i create a new namespace its working, really don't know what happen here....
If i remove it and remove the PVC & PV storage and try again in the test namespace its working, i do this in my default namespace it hit the error, so i think the default namespace can't be used....
What did you do to encounter the bug? This appears to be the same problem as reported in https://github.com/mongodb/mongodb-kubernetes-operator/issues/533 The only difference is the securityContext.
What did you expect? After applying mongodb.MongoDBCommunity.yml, I wait until
kubectl get mdbc -n mongodb
reports Running. I then shell into themongod
container and attempt to connect locally using the mongo client.What happened instead? The connection is refused and further investigation reveals mongod is not running
Operator Information
Kubernetes Cluster Information
Additional context The operator was created using the instructions provided in the repo's documentation.
mongodb.MongoDBCommunity.yml:
agent-health-status.json
Operator Logs
mongod pod logs
mongodb-agent pod logs