[DOCS-14065] Investigate changes in SERVER-52610: Verify installation prefix is added to correct location in the RPM Created: 19/Dec/20  Updated: 13/Nov/23  Resolved: 08/Mar/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.9.0, 4.4.5, 4.2.14, 4.0.25, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Andrew Feierabend (Inactive)
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-52610 Verify installation prefix is added t... Closed
Participants:
Days since reply: 3 years, 7 weeks, 4 days ago
Epic Link: DOCSP-9747

 Description   

Description

Downstream Change Summary

This change makes it possible now to relocate the installation paths of the installed RPMs using the --relocate argument. For example, to relocate the installation to opt, you would use the following arguments:

rpm --relocate /usr=/opt --relocate /var=/opt/var --relocate /etc=/opt/etc --noscripts mongodb-enterprise-server.rpm

This is true for all of the RPMs produced by the main mongodb repository, but it does not yet affect the mongodb-tools RPM, nor does it affect Compass installation paths. This change is intended to make it possible for an experienced administrator to either install a second server or install into a container root directory. The --noscripts argument is required for installation to complete, and the administrator will need to do extra work to configure and start the server.

This is not a recommended procedure unless you really know what you're doing and why you're doing it. It's also completely untested (and essentially untestable given our current setup), so this is definitely "do at your own risk" territory.

Description of Linked Ticket

Currently, users installing multiple versions of MongDB via RPM package on the same server using "--prefix <p>" still results in files being deployed to common locations.

Adding the installation prefix to the right parts of the RPM should be a fairly mechanical fix to address this.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


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