BugZero found this defect 39 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/10/2024
MongoDB Server
No affected releases provided.
No fixed releases provided.
When we test multiversion scenarios, the parameters set at the build variant level (like this one), are not being set during the instantiation of old mongod binaries (i.e. mongod-8.0, mongod-7.0, etc). According to this message, this prevents setting a parameter that could not exist on a mongod version. However, this is error-prone solution since some tests may expect a parameter to be set on all the mongod binaries of a cluster. For instance, we have had a test failure (the BF is linked to this ticket) since we expected all binaries on a cluster to have set this parameter.
Run this multiversion test locally from the master branch: buildscripts/resmoke.py run --storageEngine=wiredTiger --storageEngineCacheSizeGB=0.5 --dbpath=/tmp/testpath --mongodSetParameters='{internalQueryFrameworkControl: forceClassicEngine}' --jobs=1 --suite=sharding_last_lts_mongos_and_mixed_shards ./jstests/ sharding/query/lookup_targeting.js