Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-136667ClosedFixed
Move PPC64LE CI builds to ARM64 hosts
PPC64LE CI still runs its build and packaging stream on IBM hosts. Move the RHEL 8.1, 9, and 10 release and shared variants onto the same ARM64 cross-build strategy as s390x, while retaining native PPC64LE dbtests, integration tests, unit tests, and server-version recording. Waterfall release builds retain fully local execution and cache restrictions on the ARM64 build host.
Native resmoke tasks receive a separate PPC64LE Python environment, and publishing retains its existing test gates. Cor
Components
Build
Fixed Versions
9.1.0-rc09.1.0-rc10248.3.169.0.78.0.40
SERVER-134991ClosedFixed
Add completion log for chunk migration
Similar to [resharding|https://github.com/mongodb/mongo/blob/6d990baca59ce7cdddded93409e0266d1ac6a45a/src/mongo/db/s/resharding/resharding_coordinator.inl#L2750].
Similar to resharding, we want the log to only appear once per movechunk execution (no duplicate logs when movechunk is re-run during recovery). And potentially capture all errors encountered during moveChunk (should at least have covered cases when the countDonorMoveChunkAborted stat is incremented).
Note that in the resharding lo
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.78.0.40
SERVER-137049ClosedFixed
Define dedicated mongot circuit breaker error code
[circuit breaker]Add error code in server
[Design doc|https://docs.google.com/document/d/1jMvKhfJQ3aUja3WZRUhb_TEDJ-Ksq7rkHdf9a6bTPjg/edit?tab=t.0#heading=h.m57fkwlbz39y]
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.98.3.188.0.40
SERVER-138810In Code Review
Fix custom build CI double applying patches
Package task will fail if you try to use a patch on a custom build because it double applies it. Fix thisx.
Fixed Versions
8.0.40
SERVER-137799ClosedFixed
Preserve release binary hashes across RPM and DEB packages
RPM postprocessing can rewrite ELF symbol metadata in already finalized release binaries, making the installed binaries differ from the release tarball. Disable RPM stripping across community and enterprise package specs so packaging preserves the original bytes.
Release package tests now compare the SHA-256 hashes of installed {{mongod}} and {{mongos}} with the hashes verified against the release archive, before invoking either binary. The checks use the existing provenance eligibility and ski
Components
Packaging
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.98.3.188.0.407.0.50
SERVER-93028ClosedFixed
Remove `repeated_crash_recovery_with_history_store.js`
In repeated_crash_recovery_with_history_store.js, we set a low {color:var(--ds-text, #172b4d)}wiredTigerCacheSizeGB to stress the WT cache and create conditions for the usage of {color}{color:var(--ds-text, #172b4d)}the history store. {color}
Some options to consider: raising {color:var(--ds-text, #172b4d)}wiredTigerCacheSizeGB, disabling the write ahead log, or disabling this test on slow machines.{color}
Fixed Versions
8.1.0-rc08.0.40
SERVER-134723ClosedFixed
Fix crash if sync source resolver fails to find sync source for catchup
There seems to be a crash coming from [this log message|https://github.com/mongodb/mongo/blob/v8.0/src/mongo/db/repl/bgsync.cpp#L396]. This is logged when the sync source resolver can't [find an appropriate sync source|https://github.com/mongodb/mongo/blob/v8.0/src/mongo/db/repl/bgsync.cpp#L389]. However, {{getSyncSource()}} requires that there be a valid sync source stored in the response object and that the [return status is OK|https://github.com/mongodb/mongo/blob/v8.0/src/mongo/db/repl/sync_
Components
Replication
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.78.3.188.0.40
SERVER-137896ClosedWon't Do
remove bulk_write_without_shard_key_errors_only.js from backports required
This was removed as a part of SERVER-113344 but it shouldn't have been because on 8.0 upserts are still reported in nMatched because of a change in SERVER-103780 stemming from the unified write executor which is not backported. The test also needs to be marked multiversion incompatible to stop multiversion from running agains 7.0 which doesn't have the SERVER-113344 fix. This only needs to land on 8.0.
Fixed Versions
8.0.40
SERVER-138692In Code Review
Verify macos notary client binary checksums and signatures in Server Repo before execution
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.98.3.188.0.407.0.50
SERVER-137558ClosedFixed
[8.0] Add boolean_simplifier_tautology.js and elemmatch_empty_path.js to backport test exclusion list
Specifically to the last-patch.all section
Fixed Versions
8.0.40
SERVER-132463ClosedFixed
Clustered Index names allow null embedded bytes
Discovered via the fuzzer. Attaching a minimal reproducer. I would recommend updating the up-front validation of clustered index names.
One of the problems with storing embedded null bytes in an index name is that collStats cannot represent the name in BSON since SERVER-95279 introduced stronger checks in the server.
Affected Versions
9.0 Required
Fixed Versions
9.1.0-rc08.3.99.0.0-rc28.0.377.0.50
SERVER-125921ClosedFixed
Sharded timeseries collMod can abort without releasing participant critical sections
A sharded time-series {{collMod}} can leave shard participant critical sections held if it hits a non-retriable error after the {{kBlockShards}} phase.
{{CollModCoordinator}} enters the critical section in {{kBlockShards}} by sending {{_shardsvrParticipantBlock}} with {{ReadsAndWrites}} to shards owning chunks. It only releases that critical section later as a side effect of {{_shardsvrCollModParticipant}} in {{{}kUpdateShards{}}}, when the participant sees {{needsUnblock=true}} and calls {{{
Affected Versions
7.0.08.0.09.0.0-rc08.3.0
Fixed Versions
9.1.0-rc09.0.48.3.168.0.377.0.50
SERVER-104325ClosedFixed
[v8.0] DDL lock acquisition can hang indefinitely on secondaries
The {{setAlwaysInterruptAtStepDownOrUp_UNSAFE()}} function on the operation context is unsafe in a sense that if a stepdown happens during the run of that function, the said stepdown (and the interruption) would be missed.
If a component tries to acquire the DDL lock after it became a secondary, it will hang for 5 minutes (the default timeout for the DDL lock acquire) since the DDL lock acquisition waits for the recovery of the {{{}ShardingDDLCoordinator{}}}, what will never happen because th
Affected Versions
7.0.08.0.0
Fixed Versions
8.0.167.0.50
SERVER-139196ClosedFixed
Defer package provenance type annotations for Python 3.9 compatibility
h2. Problem
The v7.0 staging package-test driver fails during import on hosts using Python 3.9.2. Type annotations in {{buildscripts/package_test_provenance.py}} are evaluated at module import time; the PEP 604 union expression {{Path | None}} requires Python 3.10 unless annotations are postponed.
The failure happens before any package installation or package tests run. The representative RHEL 8 task reports zero test results.
h2. Observed failure
[Waterfall build|https://spruce.corp.mongodb.c
Fixed Versions
7.0.50
SERVER-121207ClosedFixed
tassert in plan enumerator when empty path and $elemMatch are used
The repro script attached reaches a tassert in the plan enumerator, "9074700: RelevantTag is not assigned to the match expression node". From what I've tried, the empty path + elemMatch seem to be required to reach this issue
Fixed Versions
9.0.0-rc08.0.378.3.187.0.50
SERVER-134008ClosedDone
Avoid cryptography sdist during Poetry bootstrap on s390x and ppc64le
h2. Problem
The {{compile_mongor}} task on the {{enterprise-rhel-83-s390x}} build variant failed in [BF-45881|https://jira.mongodb.org/browse/BF-45881] while creating the Poetry virtual environment.
The bootstrap command runs:
Because the requirements file specifies {{cryptography~=44.0.2}}, pip selected {{cryptography-44.0.3.tar.gz}} on s390x and attempted a PEP 517 metadata build. The build failed because the host did not have the {{stable-s390x-unknown-linux-gnu}} Rust toolchain installe
Fixed Versions
9.0.17.0.50
SERVER-136184ClosedFixed
Require release Evergreen distros when the Bazel build wrapper uses release configurations
h2. Problem
The Evergreen Bazel build wrapper can enable release configurations while running on a regular Evergreen distro. During review of [mongo PR #63636|https://github.com/10gen/mongo/pull/63636], s390x release compilation was moved to ARM64 builders, but the assignments used regular distros despite equivalent release distros being available. Add a runtime check to catch this configuration mistake before compilation.
h2. Proposed change
Add a shared check to {{evergreen/bazel_compile.sh}}
Components
Bazel
Fixed Versions
9.1.0-rc09.1.0-rc10248.3.169.0.78.0.377.0.50
SERVER-104438ClosedFixed
Reclaiming oplog may block stepup/stepdown
The OplogCapMaintainerThread deletes oplog with a method called reclaimOplog(), with global and RSTL locks held. This method can take a long time if there is a lot of oplog to reclaim, longer than 30 seconds, resulting in stepup or stepdown crashing due to not being able to obtain the RSTL.
Fix might be to make reclaimOplog() interruptible, or to take the global lock without the RSTL if this is safe, or both.
Fixed Versions
8.2.0-rc08.0.217.0.50
SERVER-136176ClosedFixed
Backport cross compile for zseries machines
Fixed Versions
8.3.169.0.78.0.377.0.50
SERVER-132638ClosedFixed
count with limit 0 fails on a view but works on a collection
For the {{count}} command {{limit: 0}} means no limit, and on a collection it returns the full count. The same command against a view returns error 15958, "the limit must be positive".
Negative limits are not affected. {{limit: -1}} on a view returns 1, which matches the collection, so zero is the only value that differs.
Every way of writing zero gives the error, so it does not depend on the numeric type. {{{}0{}}}, {{{}0.0{}}}, {{{}-0.0{}}}, {{NumberDecimal("0")}} and {{NumberDecimal("-0
Affected Versions
8.2.47.0.318.2.68.2.12
Fixed Versions
9.1.0-rc09.1.0-rc10229.0.48.3.168.0.377.0.50