Description of problem: We currently have the following ordering constraints collectors: Exec<| title == 'wait-for-settle' |> -> Pcmk_constraint<||> Exec<| title == 'wait-for-settle' |> -> Pcmk_resource<||> Exec<| title == 'wait-for-settle' |> -> Pcmk_property<||> Exec<| title == 'wait-for-settle' |> -> Pcmk_bundle<||> The problem here is that on rhel8 remotes are a dedicated puppet resource 'pcmk_remote'. From manifests/resource/remote.pp: if $::pacemaker::params::pcs_010 { pcmk_remote { $name: ensure => $ensure, ... } else { pcmk_resource { $name: ensure => $ensure, This means that on rhel8 we do not have the guarantee that remotes will be created after the cluster has settled. This has been observed in a real-life scenario (the wait-for-settle took place *after* the error): Mar 12 01:51:05 controller-0.redhat.local puppet-user[27085]: Error: /Stage[main]/Tripleo::Profile::Base::Pacemaker/Pacemaker::Resource::Remote[compute-0]/Pcmk_remote[compute-0]: Could not evaluate: backup_cib: Running: pcs cluster cib /var/lib/pacemaker/cib/puppet-cib-backup20200312-27084-1ewlz0x failed with code: 1 -> Error: unable to get cib To fix this we should rebase puppet-pacemaker to https://github.com/openstack/puppet-pacemaker/commit/e1f66f226a696f02d58784832235d2663c39887e
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. https://access.redhat.com/errata/RHBA-2020:2114