Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
-
Mongo 2.6.
*Location*: http://docs.mongodb.org/manual/release-notes/3.0-compatibility/#legacy-auth-model-removed
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/release-notes/3.0-upgrade/
*Screen Resolution*: 1680 x 1050
*repo*: docs
*source*: release-notes/3.0-compatibility
Mongo 2.6. *Location*: http://docs.mongodb.org/manual/release-notes/3.0-compatibility/#legacy-auth-model-removed *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/release-notes/3.0-upgrade/ *Screen Resolution*: 1680 x 1050 *repo*: docs *source*: release-notes/3.0-compatibility
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.