[SERVER-54386] mongodb 3.6.22 install fails if systemctl daemon is not running Created: 08/Feb/21 Updated: 29/Oct/23 Resolved: 19/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | 3.6.22 |
| Fix Version/s: | 4.9.0, 4.4.5, 4.2.14, 4.0.25 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Philipp Trulson | 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 | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.4, v4.2, v4.0
|
||||||||||||
| Steps To Reproduce: |
|
||||||||||||
| Sprint: | Dev Platform 2021-02-22 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The problem lies in the postinstall script which assumes that if the systemctl binary is present the daemon must be running:
The result is the error
|
| Comments |
| Comment by Githook User [ 07/May/21 ] | |||||||||||||||||||||||||||||||||||||||||||
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: (cherry picked from commit 8cf3de4ca76037e9bdace59d84f8ee7403f8a03b) | |||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 05/Mar/21 ] | |||||||||||||||||||||||||||||||||||||||||||
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: (cherry picked from commit 8cf3de4ca76037e9bdace59d84f8ee7403f8a03b) | |||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 03/Mar/21 ] | |||||||||||||||||||||||||||||||||||||||||||
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: (cherry picked from commit 8cf3de4ca76037e9bdace59d84f8ee7403f8a03b) | |||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 18/Feb/21 ] | |||||||||||||||||||||||||||||||||||||||||||
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: | |||||||||||||||||||||||||||||||||||||||||||
| Comment by Ryan Egesdahl (Inactive) [ 09/Feb/21 ] | |||||||||||||||||||||||||||||||||||||||||||
|
philipp@trulson.de This is actually a long-term solution, in that we intend the change to be permanent. We will also be fixing the package maintainer scripts, but those changes are tied to version releases, which tend to be infrequent. Changing Dockerfile doesn't address all situations where this behavior might crop up, but it should permanently resolve the one you reported. | |||||||||||||||||||||||||||||||||||||||||||
| Comment by Philipp Trulson [ 09/Feb/21 ] | |||||||||||||||||||||||||||||||||||||||||||
|
Hey Jon, thanks for the quick workaround! Yes, a longer term solution would be better, but at least it works. | |||||||||||||||||||||||||||||||||||||||||||
| Comment by Jonathan Streets (Inactive) [ 08/Feb/21 ] | |||||||||||||||||||||||||||||||||||||||||||
|
hi philipp@trulson.de,
Then building the container locally in the 3.6 directory
I will follow up with the maintainers of the docker-library repository, and our Server Team to get a longer term solution. jon |