Fix shardingtest upgradeCluster function to reflect 3.2 upgrade process

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • Sharding 10 (02/19/16)
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Shardingtest upgradeCluster upgrades mongos first and this hence the two step upgrade process is needed in jstests because mongos can not connect to mongod 3.0 or less.
      Need to fix the upgradeCluster to choose the upgrade order depending of the version it upgrades to.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: