[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:
Depends
is depended on by SERVER-34984 Update major_version_upgrade.js test ... Closed
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: SERVER-33194 Call setFCV when upgrading binary versions in test
Branch: master
https://github.com/mongodb/mongo/commit/b9b3b631d6f66a6713ab607f10defbf1c642a2a5

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