No host described in new configuration with {version: 1, term: 0} for replica set rs0 maps to this node

Yash_Babariya · 2024-07-20T11:44:44.751Z

I installed bitnami/mongodb helm chart version 15.6.12 in the EKS cluster using this below command with replicaset configuration

 helm install mongodb bitnami/mongodb --version 15.6.12 \
--set auth.rootPassword=<root_password> \
--set architecture=replicaset \
--set replicaCount=1 \
--set externalAccess.enabled=true \
--set externalAccess.autoDiscovery.enabled=true \
--set serviceAccount.create=true \
--set automountServiceAccountToken=true \
--set rbac.create=true \
--set externalAccess.service.type=LoadBalancer \
--set persistence.storageClass=gp2

Problem:- The pod was not Ready (0/1) , and the pod status was Running. Error is pod was not rs.initiate()
I saw the pod logs and got the below error message.

{“t”:{“$date”:“2024-07-19T05:44:52.000+00:00”},“s”:“W”, “c”:“QUERY”, “id”:23799, “ctx”:“ftdc”,“msg”:“Aggregate command executor error”,“attr”:{“error”:{“code”:26,“codeName”:“NamespaceNotFound”,“errmsg”:“Unable to retrieve storageStats in $collStats stage :: caused by :: Collection [local.oplog.rs] not found.”},“stats”:{},“cmd”:{“aggregate”:“oplog.rs”,“cursor”:{},“pipeline”:[{“$collStats”:{“storageStats”:{“waitForLock”:false,“numericOnly”:true}}}],“$db”:“local”}}}

Also I describe the pod then I founded the Warring message from pod.

Warning Unhealthy 51s (x505 over 75m) kubelet Readiness probe failed: Error: Not ready

After I found some blogs I found it that, MongoDB replication was not initiate

Esther_Smith · 2024-07-22T11:37:29.954Z

This post was flagged by the community and is temporarily hidden.

Yash_Babariya · 2024-08-09T14:35:29.871Z

Does any one have a solution for this solution?

Zach_Thill · 2024-11-11T03:10:03.531Z

I’m having this exact same problem.