Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-33194

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

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.7.3
    • Upgrade/Downgrade
    • Fully Compatible
    • Storage 2018-02-26

    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.

      Attachments

        Issue Links

          Activity

            People

              maria.vankeulen@mongodb.com Maria van Keulen
              maria.vankeulen@mongodb.com Maria van Keulen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: