[DOCS-6860] OpsManager 1.8.X (and older) Don't Support MongoDB 3.2 Created: 21/Dec/15 Updated: 11/Jan/17 Resolved: 07/Jan/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Peter Garafano (Inactive) | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | mms | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 8 years, 8 weeks, 2 days ago | ||||||||
| Description |
|
We need to make a note somewhere that OpsManager 2.0 is required to deploy MongoDB 3.2. |
| Comments |
| Comment by Cailin Nelson [ 21/Dec/15 ] |
|
For Monitoring, Backup or Automation of MongoDB 3.2.X deployments, Ops Manager 2.0.X+ is required. |