-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Fully Compatible
-
v4.2
-
Sharding 2021-06-14
-
45
The changes from c0142cd as part of SERVER-56961 made it so the FuzzerRestoreClusterSettings hook first restores the feature compatibility version to latestFCV. When a previous upgrade or downgrade was interrupted, the setFeatureCompatibilityVersion command is run to finish the FCV upgrade or downgrade and then the featureCompatibilityVersion server parameter and document is read to affirm the FCV upgrade or downgrade completed successfully. mongos doesn't report a featureCompatibilityVersion server parameter and so the withFCV() function throws in this case.
- is related to
-
SERVER-51333 setFeatureCompatibilityVersion should fail when downgrading from FCV 4.4 to FCV 4.2 with long collection names present
- Closed
-
SERVER-53359 jstestfuzz (mutational) fuzzer is forcing last-lts FCV during validate instead of latest
- Closed
-
SERVER-56961 [v4.4] Ensure cluster is in FCV 4.4 while running FuzzerRestoreClusterSettings hook
- Closed
- related to
-
SERVER-59158 Support running checkFCV() shell helper with mongos connection
- Closed