Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- before-branch
- branch-9.0

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Sprint:
CAR Team 2026-07-20, CAR Team 2026-08-03, CAR Team 2026-08-17
Linked BF Score:
200
CAR Domain/s:

🟩 Routing and Topology

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
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

blocks

SERVER-131278 [Join Optimization] Introduce command to dump contents of join plan cache

Closed

SERVER-133053 test_api_version_compatibility cannot run without the 9.1.0 Git tag

Open

SERVER-132952 Re-enable tests disabled due to FCV upgrade to 9.1

Open

SERVER-132996 Re-enable tests disabled due to FCV upgrade to 9.1

Open

SERVER-132957 Re-enable tests disabled due to FCV upgrade to 9.1

Backlog

SERVER-132998 Re-enable tests disabled due to FCV upgrade to 9.1

Backlog

SERVER-133004 Re-enable tests disabled due to FCV upgrade to 9.1

Backlog

SERVER-133008 Re-enable tests disabled due to FCV upgrade to 9.1

Backlog

SERVER-131690 Re-enable test disabled due to FCV upgrade to 9.1

In Code Review

SERVER-132953 Re-enable tests disabled due to FCV upgrade to 9.1

In Code Review

SERVER-133002 Re-enable tests disabled due to FCV upgrade to 9.1

In Progress

SERVER-132954 Re-enable tests disabled due to FCV upgrade to 9.1

Closed

SERVER-132955 Re-enable tests disabled due to FCV upgrade to 9.1

Closed

SERVER-132997 Re-enable tests disabled due to FCV upgrade to 9.1

Closed

SERVER-132999 Re-enable tests disabled due to FCV upgrade to 9.1

Closed

SERVER-133003 Re-enable tests disabled due to FCV upgrade to 9.1

Closed

SERVER-133022 Re-enable test disabled due to FCV upgrade to 9.1

Closed

SERVER-132935 Re-enable tests disabled due to FCV upgrade to 9.1

Needs Scheduling

SERVER-133009 Re-enable tests disabled due to FCV upgrade to 9.1

Needs Scheduling

SERVER-133010 Re-enable tests disabled due to FCV upgrade to 9.1

Needs Scheduling

SERVER-133011 Re-enable tests disabled due to FCV upgrade to 9.1

Needs Scheduling

SERVER-133012 Re-enable tests disabled due to FCV upgrade to 9.1

Needs Scheduling

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

is depended on by

SERVER-131546 Re-enable disagg multiversion suites

Needs Scheduling

SERVER-115711 Make ShardRegistry use shard UUID

Backlog

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

SERVER-133815 Ensure that BM_FIND_ONE uses a realistic IFR context

Needs Scheduling

SERVER-133889 Create a skill for handling the mechanical parts of upgrading FCV constants

Needs Scheduling

(17 blocks, 1 depends on, 1 is blocked by, 2 is depended on by, 5 related to)

Assignee:: Marco Bizzarri
Reporter:: Andrew Bui
Participants:: Andrew Bui, Githook User, Marco Bizzarri
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Jun 23 2026 05:07:10 PM UTC
Updated:: Aug 21 2026 04:14:03 PM UTC
Resolved:: Aug 12 2026 03:20:29 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty