Page MenuHomePhabricator

Add Scap3 config option to disable systemd services on secondary hosts
Closed, ResolvedPublic

Description

Scap3 allows to define a systemd service_name in a deployment config. The provided service will be restarted as part of the deployment. Scap is currently not aware of primary/secondary target hosts, which means the service will be restarted on secondary hosts and potentially cause problems.

Possible solutions include:

  • Make Scap3 aware of the type of target so it can disable the service where required
  • Use puppet to mask the service on secondary targets and make Scap3 ignore masked services Not viable, the Jenkins package cannot be updated when the service is masked

Details

TitleReferenceAuthorSource BranchDest Branch
jenkins-rel: disable jenkins service on secondary targetsrepos/releng/jenkins-deploy!36jnuchedisable-secondary-targetsmaster
deploy: disable configured `service_name` on secondary target hostsrepos/releng/scap!170jnuchedisable_service_on_secondary_hostmaster
Customize query in GitLab

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Change 947814 had a related patch set uploaded (by Jaime Nuche; author: Jaime Nuche):

[operations/puppet@production] releases jenkins: allow Scap to disable services on secondary hosts

https://gerrit.wikimedia.org/r/947814

Change 947814 merged by EoghanGaffney:

[operations/puppet@production] releases jenkins: allow Scap to disable services on secondary hosts

https://gerrit.wikimedia.org/r/947814

jnuche merged https://gitlab.wikimedia.org/repos/releng/scap/-/merge_requests/170

deploy: disable configured service_name on secondary target hosts