[SERVER-8316] Config upgrade v3 to v4 fails when old upgrade collections doesn't exist on the server Created: 24/Jan/13 Updated: 11/Jul/16 Resolved: 24/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
If a previous upgrade failed, it's possible that the previous upgrade collections are missing. We try to clean these up as part of the upgrade process, but failing to clean the collections up shouldn't abort the upgrade. |
| Comments |
| Comment by auto [ 24/Jan/13 ] |
|
Author: {u'date': u'2013-01-24T15:48:42Z', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}Message: |
| Comment by auto [ 24/Jan/13 ] |
|
Author: {u'date': u'2013-01-24T15:27:06Z', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}Message: |