diff options
| author |   Jiri Stransky <jistr@redhat.com> | 2016-03-29 14:11:08 +0200 |
|---|---|---|
| committer | Jiri Stransky <jistr@redhat.com> | 2016-03-29 14:38:27 +0200 |
| commit | 7b2e56053f6cf7535c7ae416c5cb41e7c9679924 (patch) | |
| tree | d73504efa4b5fe0764eae7143a6458203d511e57 /puppet/controller.yaml | |
| parent | dfa0b12265c573314092eb8479caca76322a9f06 (diff) | |
Don't restart Pacemaker-managed services from Puppet
We need to reload/restart services on updates/upgrades to apply any
config changes, but restarting services managed from Pacemaker from
Puppet causes problems.
For now we no-op the restart and rely on the catch-all restart after
Puppet phase.
In the future we should have a service provider for pacemaker resources
that will be using pcs. We still might have to restart services outside
Puppet due to cluster-wide orchestration issues, but we might be able to
do the restarts selectively rather than restart everything.
We also no-op the start/stop commands to be safe, as it also doesn't
make sense for Puppet to try start and stop those services when it
doesn't have knowledge about Pacemaker.
Change-Id: I95e21e10471cd7575f28c095c48150325f1414b3
Closes-Bug: #1562922
Diffstat (limited to 'puppet/controller.yaml')
0 files changed, 0 insertions, 0 deletions