[DOCS-12342] Ops Manager mongod binary deletion not referenced. Created: 08/Jan/19 Updated: 29/Oct/23 Resolved: 09/Jan/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Charles Merrill | Assignee: | Jeffrey Allen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | |||
| Participants: | |
| Days since reply: | 5 years, 5 weeks ago |
| Story Points: | 0.5 |
| Description |
DescriptionFor Ops Manager versions that still use the Deployment Version Manager, previous mongod version binaries will remain in the host systems download path after upgrading versions. This is not mentioned in the documentation. You must uncheck the old versions in Version Manager for the older binaries to be removed from the system by the Automation Agent. Note that this can be problematic if the older version(s) are still running on other systems. Details on Version Manager can be found here: In Ops Manager 4.1 and forward, the manual version manager was removed, so that step is not necessary. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Jeffrey Allen [ 09/Jan/19 ] |
|
Changes merged into v4.0 and deployed. |
| Comment by Githook User [ 09/Jan/19 ] |
|
Author: {'username': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'name': 'jeff-allen-mongo'}Message: ( Updates per Tony's feedback Updates per Tony's feedback pt 2 |
| Comment by Charles Merrill [ 09/Jan/19 ] |
|
https://github.com/10gen/mms-docs/pull/2060 |