Comment 3 for bug 1713127

So the issue seems that the stonith-enabled=false is never set and so pacemaker does not start the db and hence clustercheck fails.

On my working deployment I can see the following:
Aug 29 13:42:07 [19665] overcloud-controller-0 cib: info: cib_perform_op: ++ /cib/configuration/crm_config/cluster_property_set[@id='cib-bootstrap-options']: <nvpair id="cib-bootstrap-options-stonith-enabled" name="stonith-enabled" value="false"/>

I can't see this here, so maybe we have some dependency issues here. What is a bit odd is that in the pacemaker tripleo profile we have the following (at step1):
    class { '::pacemaker':
      hacluster_pwd => hiera('hacluster_pwd'),
    }
    -> class { '::pacemaker::corosync':
      cluster_members => $pacemaker_cluster_members,
      setup_cluster => $pacemaker_master,
      cluster_setup_extras => $cluster_setup_extras,
      remote_authkey => $remote_authkey,
    }
    if $pacemaker_master {
      class { '::pacemaker::stonith':
        disable => !$enable_fencing,
        tries => $pcs_tries,
      }
    }

The creation of the galera resource happens at step 2, so we should be guaranteed to have stonith property set to false.