[SERVER-31985] Modify and re-enable multiversion tests disabled until featureCompatibilityVersion is bumped to 3.8 Created: 15/Nov/17  Updated: 21/Feb/18  Resolved: 21/Feb/18

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Maria van Keulen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after SERVER-32597 Update "latest" FCV to be 4.0 and "la... Closed
Related
is related to SERVER-31553 Update multiversion tests on 3.6 and ... Closed
Sprint: Storage 2018-01-01, Storage 2018-02-26
Participants:

 Description   

Currently all the FCV-related multiversion tests are disabled by SERVER-31553. Some of the tests definitely can be applied to 3.6->3.8 upgrade as well but we disable them because we don't have FCV3.8 yet.



 Comments   
Comment by Maria van Keulen [ 21/Feb/18 ]

The only remaining multiversion tests that were disabled by SERVER-31553 and have not since been removed or re-enabled are major_version_upgrade.js and feature_compatibility_version_lagging_secondary.js. These tests will be re-enabled as part of SERVER-33194 and SERVER-32636, respectively.

Comment by Dianna Hohensee (Inactive) [ 09/Feb/18 ]

This may have already been resolved or is being handled by other server tickets. Check, then resolve if so.

Comment by Dianna Hohensee (Inactive) [ 17/Jan/18 ]

Can't do this until the default FCVs become 3.6 and 3.8, rather than 3.4 and 3.6. Dependent on SERVER-32597, to pull out FCV 3.4 and update the defaults.

Generated at Thu Feb 08 04:28:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.