[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: |
|
||||
| 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:
|
| 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: Signed-off-by: Sam Kleinman <samk@10gen.com> |
| 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: Signed-off-by: Sam Kleinman <samk@10gen.com> |