[DOCS-10819] Downgrade from 3.4 to 3.2 instructions do not work with auth enabled and views created Created: 21/Sep/17 Updated: 29/Oct/23 Resolved: 26/Sep/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Kevin Arhelger | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 20 weeks, 1 day ago |
| Description |
|
https://docs.mongodb.com/manual/release-notes/3.4-downgrade/ Section 2:
Users in deployments with authorization enabled cannot drop system collections. This breaks the downgrade process for anyone using auth that has ever created a view. |
| Comments |
| Comment by Githook User [ 26/Sep/17 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 26/Sep/17 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |