I’m experiencing an issue while attempting to upgrade our MongoDB Helm chart from version 10.15.2 to 12 or any. After the upgrade, the MongoDB pods fail to start. Below are the details of the error messages we’re encountering:
Current Pod Status:
After the upgrade attempt, one of the pods shows a failed liveness probe. Please see the screenshot for reference. It indicates that one container is running as 1/2, while another remains 2/2.
Logs from Describe Output
The following errors appear in the logs:
Liveness Probe Failed:
Liveness probe failed: Get "http://10.5.41.68:9216/ ": EOF
Warning - Unhealthy:
Warning Unhealthy 2m29s (x23 over 6m29s) kubelet Readiness probe failed: Get "http://10.5.41.68:9216/ ": EOF
Authentication and Connectivity Errors:
Additionally, the logs indicate authentication and connection errors, as shown in the screenshots:
- Authentication Failed: Error mentions a SCRAM-SHA-256 authentication failure with storedKey mismatch. Attaching the screenshot for your reference.
Any suggestions how we can get rid of this?