Move existing FCV feasibility checks into uasserts for upgrade/downgrade function

XMLWordPrintableJSON

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

      In the setFeatureCompatibilityVersion code there are some checks that can throw the CannotUpgrade or CannotDowngrade errors but which are not called from the _userCollectionsUassertsFor(Upgrade|Downgrade) functions (example, further example).

       

      Those checks should be moved into those functions (as documented on the FCV README). Running compatibility checks outside those functions has the risk that they may not serialize correctly with setFCV, or be caught by the dry-run mode introduced in SERVER-106841.

            Assignee:
            Anna Maria Nestorov
            Reporter:
            Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: