[DOCS-13911] [OM] Update upgrade via tar instructions Created: 06/Oct/20 Updated: 10/Aug/23 Resolved: 10/Aug/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ulrich von der Blumensaat | Assignee: | Will Pierce |
| Resolution: | Done | Votes: | 0 |
| Labels: | new-hire-ticket | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 29 weeks, 1 day ago |
| Epic Link: | DOCSP-8786 |
| Story Points: | 2 |
| Description |
DescriptionThe releases directory is not created automatically in a tar installation but if it is in the default location it will be missing after tar upgrade instructions. A customer ran into that issue ( 00694594 ) and requested an update to After discussing ways to place that information in the TSE team here is a suggested change: add: "If the Versions Directory https://docs.opsmanager.mongodb.com/current/reference/config/ui-settings/#Versions-Directory is in <install_dir> then back it up." and then also add under step 5 ( https://docs.opsmanager.mongodb.com/v4.4/tutorial/upgrade-ops-manager/#on-each-onprem-host-restore-the-backed-up-logs-and-configuration-files-into-the-onprem-installation-directory ) : add:
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Peter Vertenten [ 18/Jul/23 ] |
|
ulrich.blumensaat@mongodb.com did confirm this to still be an issue. The mv step deletes the old mongod-release dir. His suggestion to copy it back inplace after the tar extraction makes sense. |
| Comment by Will Pierce [ 13/Jul/23 ] |
|
peter.vertenten@mongodb.com We did some investigation, and weren't able to determine if this is still applicable.
Are users still having trouble with this `mongodb-releases` directory? It isn't included in the most recent tar downloads. |