[DOCS-5749] Comment on: "manual/release-notes/3.0-compatibility.txt" Created: 30/Jun/15 Updated: 08/Dec/16 Resolved: 02/Jul/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mongo 2.6. Location: http://docs.mongodb.org/manual/release-notes/3.0-compatibility/#legacy-auth-model-removed |
||
| Participants: | |
| Days since reply: | 8 years, 32 weeks, 6 days ago |
| Description |
|
After installing 3.0 on top of an existing 2.6, we get the error that the authorization shema must be upgraded. However, when we query db.system.version.find() on the admin-db, we get no response, which suggests we do not use auth and everything should be okay. Unfortunately, this is not the case and I can not find any helpful information on what to do now. |
| Comments |
| Comment by Githook User [ 02/Jul/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |