Update major_version_upgrade.js test to call setFeatureCompatibilityVersion when applicable before upgrading the binary version

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.3
    • Affects Version/s: None
    • Component/s: Upgrade/Downgrade
    • Fully Compatible
    • Storage 2018-02-26
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Maria van Keulen
            Reporter:
            Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: