Comment 8 for bug 1562922

Reviewed: https://review.openstack.org/298847
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=f3215d28ba6693e8e513cc3ae2aba3e500a0a4f0
Submitter: Jenkins
Branch: stable/mitaka

commit f3215d28ba6693e8e513cc3ae2aba3e500a0a4f0
Author: Jiri Stransky <email address hidden>
Date: Tue Mar 29 14:11:08 2016 +0200

    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
    (cherry picked from commit 7b2e56053f6cf7535c7ae416c5cb41e7c9679924)