Ops Manager 4.2 upgrade MongoDB version block on shutdown delayed secondary node

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Declined
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      * Ops Manager 4.2.4

      I use Ops Manager 4.2.4 to upgrade MongoDB(shard cluster, with delayed secondary node exist in shard) version from 4.2 to 4.2.1

      • If upgrade enterprise version(4.2-ent to 4.2.1-ent) the upgrade failed, block on shutdown the delayed secondary process (more details refer to attachments)
      • if upgrade community version(4.2 to 4.2.1), upgrade success. 

        1. ops-upgrade-mongodb-enterprise.png
          ops-upgrade-mongodb-enterprise.png
          215 kB

            Assignee:
            Unassigned
            Reporter:
            Kylin Soong (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: