mongos with --upgrade and missing --auth flag prints "config servers not in sync" message

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.4.5, 2.5.0
    • Affects Version/s: 2.4.0
    • Component/s: Logging
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      On a sharded cluster with auth turned on, start up a 2.4 mongos with --upgrade to do the metadata upgrade but forget to include --auth:

      [mongosMain] ERROR: config servers not in sync! no config servers reachable

      The error is confusing, the config servers are in sync but mongos just can't connect to them because of missing auth params. Should be some kind of auth error message instead.

              Assignee:
              Greg Studer (Inactive)
              Reporter:
              Michael O'Brien
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: