Stop running mcollective
The puppet-agent package has added mcollective as a service that just gets run, so we have a ton of servers, basically anything that has been rebooted since the package update, that are running an mcollective daemon that is trying and failing to connect to the mcollective system that does not exist. Add a disabling of the mcollective unit to the disable-puppet-agent role. Also - add disable-puppet-agent everywhere. We'll re-remove it later, but let's make sure we've got this turned off on all of our non-puppet hosts now too. Change-Id: I5c6235e88e5aac3fee85f58d762023c793635f42
This commit is contained in:
parent
33e48396d1
commit
8193a01742
@ -13,6 +13,7 @@
|
||||
- timezone
|
||||
- unbound
|
||||
- exim
|
||||
- disable-puppet-agent
|
||||
|
||||
# Do not run firewall rules on kubernetes hosts, they are managed by k8s-on-openstack.
|
||||
# TODO(mordred) snmpd should be able to be re-added to kubernetes hosts but we will
|
||||
|
@ -10,3 +10,11 @@
|
||||
name: puppet
|
||||
enabled: no
|
||||
state: stopped
|
||||
failed_when: false
|
||||
|
||||
- name: Disable the mcollective service
|
||||
service:
|
||||
name: mcollective
|
||||
enabled: no
|
||||
state: stopped
|
||||
failed_when: false
|
||||
|
Loading…
Reference in New Issue
Block a user