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

change in output of getParameter command for featureCompatibilityVersion in 3.6.0-rc2 is breaking automation agent

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.0-rc2
    • Component/s: Internal Code
    • Labels:
      None
    • Fully Compatible
    • ALL

      output of

      db.adminCommand( { getParameter : 1, "featureCompatibilityVersion" : 1 } )
      

      in mongodb 3.6 rc1:

      {
      	"featureCompatibilityVersion" : "3.6",
      	"ok" : 1,
      	"operationTime" : Timestamp(1509635213, 1),
      	"$clusterTime" : {
      		"clusterTime" : Timestamp(1509635213, 1),
      		"signature" : {
      			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
      			"keyId" : NumberLong(0)
      		}
      	}
      }
      

      output in mongodb 3.6 rc2:

      { "featureCompatibilityVersion" : { "version" : "3.6" }, "ok" : 1 }
      

      Notice that "featureCompatibilityVersion" was a string in rc1 and its a map in rc2.
      Automation agent expects it to be a string. Because of which it is unable to deploy 3.6 rc2.
      It probably affects backup as well.

            Assignee:
            Unassigned Unassigned
            Reporter:
            ankur.srivastava@mongodb.com Ankur Srivastava (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: