Downgrade Mongo not working for Cloud Automation

We are currently running version 5.0 of mongoDB community edition and when viewing this through Cloud Manager is appears as this. We need to downgrade back to 4.4. I have been trying to follow this formal guide: https://www.mongodb.com/docs/manual/release-notes/5.0-downgrade-replica-set/ When I have completed all the steps and restart the mongodb node and services, once the Cloud Manager automation agent gets the server running again, it still appears as version 5.0.

Am I missing some kind of config that needs to be set. Furthermore, when I have downloaded and installed the mongo binaries, running a mongod --version typically shows me 4.4?

At this step in the documentation, they talk about replacing the 5.0 binary with the 4.4 binary, how can I actually check that I have done this correctly? REF: https://www.mongodb.com/docs/manual/release-notes/5.0-downgrade-replica-set/#downgrade-secondary-members-of-the-replica-set

After you downgrade the server, without involving automation, are you seeing the desired version in db.version()?

If yes, it might be that Cloud Manager automation is not aware of the downgrade. Note that the downgrade procedure you linked doesn’t involve automation, so this is a possibility.

If you’re using Cloud Manager, then the page Change the Version of MongoDB — MongoDB Cloud Manager might be more relevant.

However, if this is not solving your issue, please log into your MongoDB Cloud account and open a support ticket.

At this step in the documentation, they talk about replacing the 5.0 binary with the 4.4 binary, how can I actually check that I have done this correctly?

If you connect to the server using mongosh and execute db.version() it should return the server version that is running.

Best regards
Kevin

2 Likes