Description of problem:
In the case pacemaker-remote (OS::TripleO::Services::PacemakerRemote profile) node is being deployed within composable roles topology we should lower pacemaker property of cluster-recheck-interval to much lower value from default value which is 15mins. The reason is that even though we set ocf:pacemaker:remote attribute reconnect_interval to 60s it's not guaranteed to be performed more frequently than the value of the cluster-recheck-interval cluster option and the consequence is that in a case of failover pacemaker_remote node is reported as down those 15mins at least even though it may be back online after fencing withint a minute.
We do set that property to 60s with Instance HA topology.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy composable roles with a node which has OS::TripleO::Services::PacemakerRemote
2. Reset the node
Node is being reported as offline more than 15 minutes even though It comes back online within a minute
Master merged. Linking the ocata backport here instead.
Verified on puppet-tripleo-6.3.0-12. The property is set to 60 seconds once topology with remote pacemaker nodes is used.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.