Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Submitted
Categories Enterprise Advanced
Created by Guest
Created on Feb 26, 2025

deployment metadata resync

Ops Manager needs a way to resync deployments' metadata from the console (or command line, or API), rather than direct undocumented CURD operations in AppDB. My reason for this suggestion: See Case: 01438273. One of my deployments had duplicate entries for all 3 nodes. We suspect that happened because we were initially using short name hostnames in the deployment's replica set definition and later changed that to FQDN hostnames. The original entries should have been removed from the AppDB collection, but instead they remained there indicating version 4.0.26, while new ones were created, which were then successively updated as the deployment got upgraded. When I tried to upgrade Ops Manager to v 8.0, it refused to restart because OM8 cannot handle MongoDB versions <4.4. The solution was to manually run a deleteMany operation in the AppDB which had to be provided by the development team.