[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   

Description

I 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:
IMPORTANT
It is crucial that you back up the existing conf-mms.properties and gen.key files because the upgrade process will delete existing data.

2) In Step 3:
The installer preserves the existing conf-mms.properties configuration file and names the new configuration file conf-mms.properties.rpmnew. Both are located in /opt/mongodb/mms/conf/.

 

Scope of changes

Impact to Other Docs

MVP (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: (DOCS-12313): Fixed RPM upgrade contradiction.
Branch: one-agent-prep
https://github.com/10gen/mms-docs/commit/9779e7d05102b6c99c93daf1be6871be78ae2271

Comment by Githook User [ 05/Jan/19 ]

Author:

{'username': 'atsansone', 'email': 'tony.sansone@mongodb.com', 'name': 'Anthony Sansone'}

Message: (DOCS-12313): Fixed RPM upgrade contradiction.
Branch: master
https://github.com/10gen/mms-docs/commit/ed21c7448e038a7368ad3af0d338b43f179d9b66

Generated at Thu Feb 08 08:04:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.