Bug #15538
closed
Update component .service files
Added by Eric Biagiotti over 4 years ago.
Updated over 4 years ago.
Assigned To:
Eric Biagiotti
Release relationship:
Auto
Description
Component .service files (e.g. arvados-ws.service) have AssertPathExists, pointing to legacy config files. Update these to point to the cluster config, since we recommend deleting legacy config files.
- Related to Idea #13648: [Epic] Use one cluster configuration file for all components added
- Target version set to 2019-11-20 Sprint
- Assigned To set to Eric Biagiotti
- Status changed from New to In Progress
Just searched the repo for "AssertPathExists" and I get the following:
- arvados-controller.service, arvados-dispatch-cloud.service, and arvados-health.service all assert that the new cluster config exists at
/etc/arvados/config.yml. This is correct since these only work with the cluster config.
- arvados-node-manager.service - Checks for
/etc/arvados-node-manager/config.ini. This is also correct since node-manager is going away and isn't in the cluster config.
Subsequently, no changes are needed.
Nit: you could remove the commented AssertPathExists on services/dockercleaner/arvados-docker-cleaner.service.
Other than that, it seems that this issue was gradually fixed from other related stories, thanks!
Lucas Di Pentima wrote:
Nit: you could remove the commented AssertPathExists on services/dockercleaner/arvados-docker-cleaner.service.
Other than that, it seems that this issue was gradually fixed from other related stories, thanks!
Removed @ 7e23ed42b6e4eab1dd5e39ece5b0830b740bab1e
- Status changed from In Progress to Resolved
Also available in: Atom
PDF
Updated by Eric Biagiotti 
Updated by 
Updated by 
Updated by