[DOCS-12313] Preservation of conf-mms.properties file on upgrade Created: 03/Jan/19 Updated: 29/Oct/23 Resolved: 05/Jan/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Benjamin Ogden (Inactive) | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
https://docs.opsmanager.mongodb.com/current/tutorial/upgrade-on-prem-with-rpm-packages/ |
||
| Participants: | |
| Days since reply: | 5 years, 5 days ago |
| Epic Link: | DOCSP-1743 |
| Story Points: | 0.2 |
| Description |
DescriptionI think the Ops Mgr upgrade documentation could be a little clearer regarding the preservation of the conf-mms.properties file. See https://docs.opsmanager.mongodb.com/current/tutorial/upgrade-on-prem-with-rpm-packages/ These two sections seem to conflict- 1) End of Upgrade Path section: 2) In Step 3:
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 09/Feb/19 ] |
|
Author: {'name': 'Anthony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}Message: ( |
| Comment by Githook User [ 05/Jan/19 ] |
|
Author: {'username': 'atsansone', 'email': 'tony.sansone@mongodb.com', 'name': 'Anthony Sansone'}Message: ( |