[SERVER-61972] Multiversion test suites using useRandomBinVersionsWithinReplicaSet option should not default to using lastLTSFCV Created: 09/Dec/21  Updated: 29/Oct/23  Resolved: 02/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc10

Type: Bug Priority: Critical - P2
Reporter: Jason Chan Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.1, v6.0
Sprint: STM 2022-01-10, STM 2022-01-24, DAG 2022-06-13
Participants:
Linked BF Score: 149
Story Points: 2

 Description   

Currently, replica_sets_multiversion and sharding_multiversion will use the useRandomBinVersionsWithinReplicaSet test option to randomize the binary versions used in each test. Initially, we only had testing between lastLTS and latest versions, so ReplSetTest would always default to set lastLTS as the FCV if the option is passed in. However, PM-1803 introduced testing between last-continuous and latest versions, which means we need to update the test infrastructure to also check the value being passed into the option.



 Comments   
Comment by Githook User [ 09/Jun/22 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-61972 un-delete version check for mongod options
Branch: v6.0
https://github.com/mongodb/mongo/commit/90a5f12cb11ea74e84f44aad5d2779d9b12673a6

Comment by Githook User [ 08/Jun/22 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-61972 ensure useRandomBinVersionsWithinReplicaSet's respected
Branch: v6.0
https://github.com/mongodb/mongo/commit/10776658a7b9c6a426222bd4df99966a5973e72d

Generated at Thu Feb 08 05:53:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.