[SERVER-52610] Verify installation prefix is added to correct location in the RPM Created: 03/Nov/20 Updated: 29/Oct/23 Resolved: 19/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.4.5, 4.2.14, 4.0.25 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | April Schoffer | Assignee: | Ryan Egesdahl (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Backport Requested: |
v4.4, v4.2, v4.0
|
||||||||||||||||||||||||
| Sprint: | Dev Platform 2020-11-16, Dev Platform 2020-11-30, Dev Platform 2020-12-14, Dev Platform 2020-12-28 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 84 | ||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 12/May/21 ] | |
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: We were not using directory macros in the RPMs, which meant that the (cherry picked from commit 9aba0cac770d87d36cf0f0d19a1be06e73312221) | |
| Comment by Githook User [ 12/May/21 ] | |
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: Revert " This reverts commit 51304bb545840ef0b62a6445b1060559ab831ea1. | |
| Comment by Githook User [ 07/May/21 ] | |
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: We were not using directory macros in the RPMs, which meant that the (cherry picked from commit 9aba0cac770d87d36cf0f0d19a1be06e73312221) | |
| Comment by Githook User [ 05/Mar/21 ] | |
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: We were not using directory macros in the RPMs, which meant that the (cherry picked from commit 9aba0cac770d87d36cf0f0d19a1be06e73312221) | |
| Comment by Githook User [ 05/Mar/21 ] | |
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: We were not using directory macros in the RPMs, which meant that the (cherry picked from commit 9aba0cac770d87d36cf0f0d19a1be06e73312221) | |
| Comment by Ryan Egesdahl (Inactive) [ 19/Dec/20 ] | |
|
With this change, you should now be able to use the --relocate argument with rpm to install the server into another root. This does not affect Compass installations, nor does it affect mongodb-tools, which is handled by another repository. An example command line to install into opt looks like this:
Alternatively, you may be able to use yum --installroot=/opt if you are installing into a chroot environment (such as a container root directory). Keep in mind, the default configuration installed will not work, nor will the server auto-start on boot. It's up to you to set all of that up, and you're definitely in "experienced administrator doing custom things" territory if you choose to do all of this. We're also not able to effectively test this change at this time, either, for the aforementioned reasons. It should go without saying that this is not a recommended procedure by any means unless you really know what you are doing and why you're doing it. | |
| Comment by Githook User [ 19/Dec/20 ] | |
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: We were not using directory macros in the RPMs, which meant that the |