[SERVER-33194] Update major_version_upgrade.js test to call setFeatureCompatibilityVersion when applicable before upgrading the binary version Created: 08/Feb/18 Updated: 29/Oct/23 Resolved: 21/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Maria van Keulen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Storage 2018-02-26 | ||||||||
| Participants: | |||||||||
| Description |
|
Presently, the major_version_upgrade.js test only calls setFeatureCompatibilityVersion to ensure a featureCompatibilityVersion document exists before upgrade to 3.6, since as of 3.6 mongod fails to startup without this document. This test should be modified to always set the featureCompatibilityVersion to the version that corresponds to the current binary version (i.e., 3.6 mongod should set the fCV to 3.6) before upgrading to the following binary version. This is only necessary for versions 3.4 to latest, since the featureCompatibilityVersion was introduced in 3.4. |
| Comments |
| Comment by Githook User [ 21/Feb/18 ] |
|
Author: {'email': 'maria@mongodb.com', 'name': 'Maria van Keulen', 'username': 'mvankeulen94'}Message: |