[SERVER-37371] apt-get upgrade clobbers user modified service files Created: 28/Sep/18  Updated: 27/Oct/23  Resolved: 30/Nov/18

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mathew Robinson (Inactive) Assignee: Backlog - Build Team (Inactive)
Resolution: Works as Designed Votes: 0
Labels: build-planned
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Build
Operating System: ALL
Sprint: Build 2018-10-22, Build 2020-03-23
Participants:

 Description   

From the mongodb-user mailing list:

Hello,

We have a production cluster on 4.0 (one shard replicaset, one config replicaset, numbers of app servers/mongos nodes). Have just triggered the upgrade via apt-get. We noticed that in 4.0.0 to 4.0.1 our mongod.service files were getting clobbered, and losing the --replSet xxx in the ExecStart line. In preparation this time, we removed all write access (chmod a-w) from this file ahead of the upgrade, although the process still blew this away and back to default, causing our cluster not to come back up.

Is there any way we can stop this in the future? Having to go back and reconfigure the start up services every time we do an update is an absolute pain. Any suggestions to avoid this very much appreciated.

Cheers


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