[SERVER-8844] mongos with --upgrade and missing --auth flag prints "config servers not in sync" message Created: 04/Mar/13 Updated: 11/Jul/16 Resolved: 11/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.4.0 |
| Fix Version/s: | 2.4.5, 2.5.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael O'Brien | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
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:
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. |
| Comments |
| Comment by auto [ 20/Jun/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by auto [ 11/Mar/13 ] |
|
Author: {u'date': u'2013-03-04T23:05:47Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |