[SERVER-13968] Report invalid collection options in "<db>.system.namespaces" in upgrade checker Created: 16/May/14 Updated: 10/Dec/14 Resolved: 20/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shaun Verch | Assignee: | Matt Dannenberg |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
The tickets The issue is that the collection options in "<db>.system.namespaces" can have fields in it that are invalid but not checked in 2.4. Since 2.6 has stricter validation, this causes problems with upgrading (manifested in the two tickets above). Also need to add startup warning with remediation steps for this scenario. See |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 20/May/14 ] |
|
See |