Automation Suite
2022.10
false
Banner background image
Automation Suite Installation Guide
Last updated Apr 24, 2024

MongoDB Pod Fails to Upgrade From 4.4.4-ent to 5.0.7-ent

Description

When upgrading from Automation Suite 2021.10 to 2022.10, the MongoDB pod is stuck is rolling update and cannot move from version 4.4.4-ent to 5.0.7-ent. Only one pod is available, and it is failing the readiness check.

Solution

To check the MongoDB Agent logs, run the following command:

kubectl get pods -n mongodb
Use the pod name and get log for that pod
kubectl logs <pod-name> -n mongodb -c mongodb-agent
In the Agent logs if we are seeing below line then the upgrade hasn't been successful
  ['currentState.Version = 4.4.4-ent is equal to desiredState.Version = 5.0.7-ent' = false]kubectl get pods -n mongodb
Use the pod name and get log for that pod
kubectl logs <pod-name> -n mongodb -c mongodb-agent
In the Agent logs if we are seeing below line then the upgrade hasn't been successful
  ['currentState.Version = 4.4.4-ent is equal to desiredState.Version = 5.0.7-ent' = false]

To fix the issue, take the following steps:

  1. Disable auto-sync in ArgoCD. Go to Applications > MongoDB > AppDetails > Summary, and click Disable Auto-Sync.
  2. The MongoDB sts definition is still using the old MongoDB localhost:30071/mongodb/mongodb-enterprise-appdb-database:4.4.4-ent image. Edit the definition to use version 5.0.7-ent. Save it and sync it.
  3. Delete the old MongoDB pod.
  4. The pods should come up with MongoDB version 5.0.7-ent.
  • Description
  • Solution

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.