Add test coverage for scenarios in which we have garbage entries in config.databases

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.1, v8.0
    • CAR Team 2025-06-09, CAR Team 2025-06-23, CAR Team 2025-07-07
    • 0
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Recently it was discovered that some clusters could have unexpected documents ( garbage) in config.databases in particular we observed (AF-1692) that customer coming from old versions of mongodb (< 5.0 ) could have an entry in config.databases for the `admin` db even if today is impossible to create this database that is considered internal.

      The goal of this ticket is to extend our testing coverage to include this scenario.
      One option could be to artifically inject these type of unexpected document in some of our core passthrough suites so that we ensure that normal workflow and functionality will work as expected even in the presence of those unexpected entries in config.databases.

              Assignee:
              Marcos José Grillo Ramirez
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: