-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Fully Compatible
-
ALL
-
STM 2018-12-17
-
14
-
2
SERVER-36718 made the changes so that we can use forceValidationWithFeatureCompatibilityVersion to upgrade the servers before validating the collections. But BF-10462 is a case when a downgrade in the test was interrupted and there is no way for the validation hook to start the upgrade in the middle of a downgrade. Therefore, the validation hook should first downgrade and then upgrade in this case.
- causes
-
SERVER-44613 ValidateCollections hook does not call setFCV(4.2) if a test leaves the FCV at "upgrading to 4.4"
- Closed
- is related to
-
SERVER-36718 Validation hook should upgrade before validating index consistency
- Closed
-
SERVER-43627 Remove v4.2 FCV handling from ValidationCollections JS test hook
- Closed