So we see that:
1) pcsd gets started by puppet running on the host:
Apr 29 09:52:41 node-0000072019 puppet-user[16055]: (/Stage[main]/Tripleo::Profile::Base::Kernel/Exec[rebuild initramfs]) Triggered 'refresh' from 37 events
Apr 29 09:52:41 node-0000072019 puppet-user[16055]: (/Stage[main]/Tripleo::Profile::Base::Kernel/Sysctl::Value[net.nf_conntrack_max]/Sysctl_runtime[net.nf_conntrack_max]/val) val changed '262144' to '500000'
Apr 29 09:52:41 node-0000072019 puppet-user[16055]: (/Stage[main]/Tripleo::Profile::Base::Pacemaker/Systemd::Unit_file[docker.service]/File[/etc/systemd/system/resource-agents-deps.target.wants/docker.service]/ensure) created
Apr 29 09:52:41 node-0000072019 puppet-user[16055]: (/Stage[main]/Tripleo::Profile::Base::Pacemaker/Systemd::Unit_file[rhel-push-plugin.service]/File[/etc/systemd/system/resource-agents-deps.target.wants/rhel-push-plugin.service]/ensure) created
Apr 29 09:52:41 node-0000072019 usermod[23255]: change user 'hacluster' password
Apr 29 09:52:41 node-0000072019 puppet-user[16055]: (/Stage[main]/Pacemaker::Corosync/User[hacluster]/password) changed password
Apr 29 09:52:41 node-0000072019 usermod[23262]: add 'hacluster' to group 'haclient'
Apr 29 09:52:41 node-0000072019 usermod[23262]: add 'hacluster' to shadow group 'haclient'
Apr 29 09:52:41 node-0000072019 puppet-user[16055]: (/Stage[main]/Pacemaker::Corosync/User[hacluster]/groups) groups changed '' to ['haclient']
Apr 29 09:52:42 node-0000072019 systemd[1]: Reloading.
Apr 29 09:52:42 node-0000072019 systemd[1]: Starting PCS GUI and remote configuration interface...
Apr 29 09:52:42 node-0000072019 systemd[1]: Started PCS GUI and remote configuration interface.
Apr 29 09:52:43 node-0000072019 puppet-user[16055]: (/Stage[main]/Pacemaker::Service/Service[pcsd]/ensure) ensure changed 'stopped' to 'running'

2) After pcsd service started, nothing else seems to be observed in the logs at all
3) What we do know is that puppet was still running because in pstree we have:
           |           |-sshd(8926)---sshd(8929)---sh(16041)---sudo(16050)---sh(16052)---python(16053)---python(16054)---puppet(160+

So likely puppet is hanging *somewhere*.

From the pcsd logs we see the following last messages:
I, [2020-04-29T10:52:44.742198 #23294]  INFO -- : Running: /usr/sbin/pcs status nodes corosync
I, [2020-04-29T10:52:44.742248 #23294]  INFO -- : CIB USER: hacluster, groups: 
I, [2020-04-29T10:52:45.097004 #23294]  INFO -- : Return Value: 1
I, [2020-04-29T10:52:45.097178 #23294]  INFO -- : Config files sync skipped, this host does not seem to be in a cluster of at least 2 nodes

I.e. after the pcsd service started it seems unlikely that we ran any new commands at all. Because normally pcsd logs most of the commands that are run via pcs.

So puppet is busy doing *something*, although even from the top.log I cannot see any interesting puppet child processes that could be hanging:
  16053 root      20   0   88380   8180   3664 S   0.0  0.1   0:00.04 python
  16054 root      20   0  103584  11128   3896 S   0.0  0.1   0:00.74 python
  16055 root      20   0  410488 107196  14864 S   0.0  1.3   0:09.10 puppet

In terms of packages we have:
pacemaker-1.1.21-4.el7.x86_64
corosync-2.4.5-4.el7.x86_64 
pcs-0.9.168-4.el7.centos.x86_64
libqb-1.0.1-9.el7.x86_64

They seem stock rhel-7.8

puppet-pacemaker-0.7.3-0.20190930085227.447cef0.el7.noarch is fairly old and has not changed recently. 

Can we get puppet logs set to debug for this job?