-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2026-07-20, CAR Team 2026-08-03
-
200
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
At the time of running 9.0.0-alpha1, create FCV upgrade PR pointing to master branch, run a patch to test it. Please reference: WRITING-8774 Changes to "Guide to Updating FCV Constants" for non-Major Releases for more details.
Note: This must be completed before tagging the master branch with the next alpha tag or the build will become very red.
Immediately after branching 9.0, tag the commit in master that upgraded the FCV with 9.1.0-alpha0 by using the following command:
mr git tag-release --commit <hash> --version 9.1.0-alpha0
- depends on
-
SERVER-131654 Tolerate calling cmc without secondaryCheckMode for multiversion suites
-
- Closed
-
- is blocked by
-
SERVER-131892 Force checkpoint past FCV transition in ReplSetTest multiversion initiate
-
- Closed
-
- related to
-
SERVER-130864 Code should not assume that kLastLTS != kLastContinuous
-
- Closed
-
-
SERVER-130944 Remove mongot* tests which will fail once 9.0 becomes lastLTSFCV
-
- Closed
-
-
SERVER-131546 Re-enable disagg multiversion suites
-
- Needs Scheduling
-