yes, I can see from logs that Corosync failed to up and run:
./node-32.domain.tld/puppet-apply.log:2014-11-05T11:09:10.703074+00:00 info: (/Stage[corosync_setup]/Corosync/Package[corosync]) Evaluated in 0.00 sec
onds
./node-32.domain.tld/puppet-apply.log:2014-11-05T11:09:11.001988+00:00 debug: (Puppet::Type::Cs_property::ProviderCrm) Corosync not ready, retrying
...
./node-32.domain.tld/puppet-apply.log:2014-11-05T11:11:08.988330+00:00 debug: (Puppet::Type::Cs_property::ProviderCrm) Corosync not ready, retrying
yes, I can see from logs that Corosync failed to up and run: 32.domain. tld/puppet- apply.log: 2014-11- 05T11:09: 10.703074+ 00:00 info: (/Stage[ corosync_ setup]/ Corosync/ Package[ corosync] ) Evaluated in 0.00 sec 32.domain. tld/puppet- apply.log: 2014-11- 05T11:09: 11.001988+ 00:00 debug: (Puppet: :Type:: Cs_property: :ProviderCrm) Corosync not ready, retrying 32.domain. tld/puppet- apply.log: 2014-11- 05T11:11: 08.988330+ 00:00 debug: (Puppet: :Type:: Cs_property: :ProviderCrm) Corosync not ready, retrying
./node-
onds
./node-
...
./node-
caused this failure