summaryrefslogtreecommitdiffstats
path: root/manifests/profile/base/neutron/linuxbridge.pp
diff options
context:
space:
mode:
authorMichele Baldessari <michele@acksyn.org>2017-08-23 17:45:41 +0200
committerMichele Baldessari <michele@acksyn.org>2017-08-23 17:55:09 +0200
commit17396dcea8c8597e20f19b1f5867cb67554133ce (patch)
tree21003a473c4a7b6edeba5200b71956b749561129 /manifests/profile/base/neutron/linuxbridge.pp
parentab48d3a438845f1fe7a862cb1396963e7ca754e2 (diff)
Use resource collector for the fencing -> stonith ordering
Change Ifef08033043a4cc90a6261e962d2fdecdf275650 moved the stonith property definition to the pacemaker_master node. This means that the Class['tripleo::fencing'] -> Class['pacemaker::stonith'] ordering breaks on non-boostrap pacemaker nodes because the pacemaker::stonith property is not defined there any longer. Let's fix this by simply using a resource collector and set the ordering on that instead of adding yet anoth if statement. Ordering on enablement of stonith is actually more correct formally. Tested this on a broken setup successfully. Closes-Bug: #1712605 Change-Id: I616d340bdf75da9d9eb8b83b2e804dff3d07d58e
Diffstat (limited to 'manifests/profile/base/neutron/linuxbridge.pp')
0 files changed, 0 insertions, 0 deletions