summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXiangyu Yao <xiangyu.yao@mongodb.com>2018-10-19 10:46:16 -0400
committerXiangyu Yao <xiangyu.yao@mongodb.com>2018-10-23 13:40:19 -0400
commitb0d12219828e72dbc59ede95cc267a8c4eafbc2f (patch)
tree55efc1e952addbdfc779be5f1ede52e3aaa4f2bd
parent4410706bef6463369ea2f42399e9843903b31923 (diff)
downloadmongo-b0d12219828e72dbc59ede95cc267a8c4eafbc2f.tar.gz
SERVER-37647 Validation hook sets FCV to 3.4 no matter what version it currently is
-rw-r--r--jstests/hooks/run_validate_collections.js13
1 files changed, 7 insertions, 6 deletions
diff --git a/jstests/hooks/run_validate_collections.js b/jstests/hooks/run_validate_collections.js
index e0292740b97..55fc6a02ab3 100644
--- a/jstests/hooks/run_validate_collections.js
+++ b/jstests/hooks/run_validate_collections.js
@@ -108,12 +108,13 @@
}
}
- if (originalFCV !== jsTest.options().forceValidationWithFeatureCompatibilityVersion) {
- assert.commandWorked(adminDB.adminCommand({
- setFeatureCompatibilityVersion:
- jsTest.options().forceValidationWithFeatureCompatibilityVersion
- }));
- }
+ // The sharded cluster could be in a state where the config servers are in FCV 3.4 but the
+ // shard servers are in FCV 3.2. Therefore, we set the FCV to
+ // forceValidationWithFeatureCompatibilityVersion even if it is the same as originalFCV.
+ assert.commandWorked(adminDB.adminCommand({
+ setFeatureCompatibilityVersion:
+ jsTest.options().forceValidationWithFeatureCompatibilityVersion
+ }));
}
try {