[DOCS-3321] Upgrade MongoDB to 2.6 does not note Upgrade User Authorization Data to 2.6 Format is a required step Created: 01/May/14  Updated: 16/Mar/15  Resolved: 15/Sep/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.11

Type: Bug Priority: Major - P3
Reporter: Sherry Ger Assignee: Michael Paik
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 9 years, 22 weeks, 2 days ago

 Description   

The Upgrade MongoDB to 2.6 document does not mention Upgrade User Authorization Data to 2.6 Format is a required step. If a customer is upgrading a sharded cluster with authentication enabled and has users created in MongoDB 2.4, then Upgrade User Authorization Data to 2.6 Format is a must. Without this step, any user administration operation will produce an error like the following:

Error: User and role management commands require auth data to have schema version 3 but found 1



 Comments   
Comment by Githook User [ 15/Sep/14 ]

Author:

{u'username': u'mpaik', u'name': u'Michael Paik', u'email': u'michael.paik@10gen.com'}

Message: DOCS-3321 - more of the same

Signed-off-by: Sam Kleinman <samk@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/23e08ab92a69a7d04e508fb67d2df5a1744c5c02

Comment by Githook User [ 15/Sep/14 ]

Author:

{u'username': u'mpaik', u'name': u'Michael Paik', u'email': u'michael.paik@10gen.com'}

Message: DOCS-3321 - added bold '*must* also upgrade the authorization model'

Signed-off-by: Sam Kleinman <samk@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/690d3f7120d46a434d8009a345106287ad5bd965

Generated at Thu Feb 08 07:45:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.