Investigate transitioning_replicaset_incompatible exclusion usages

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-11-24
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-112425 introduced a new passthrough suite that runs on a replicaset started as --shardsvr but not added to a cluster.
      In order to make evergreen green, we had to exclude some tests with the transitioning_replicaset_incompatible tag.
      Most of the issues are coming from

      • setClusterParameter not going through the router (ofc, bc there is no any)
      • implicitCollectionCreation not going through a coordinator
      • running operations that are waiting for the sharding state, but don't have any yet (like refresh session cache)

      This investigation is about to check each error case-by-case and figure out if CAR can fix it, some other teams should fix it or we have to live with that exclusion for a while and open the corresponding tickets.

            Assignee:
            Wolfee Farkas
            Reporter:
            Wolfee Farkas
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: