Service failed to load 'pacemaker'.

[Anastasia Palkina]

"build_id": "2014-08-05_02-01-14",
"ostf_sha": "a3fa823ea0e4e03beb637ae07a91adea82c33182",
"build_number": "393",
"auth_required": true,
"api": "1.0",
"nailgun_sha": "5d1e8e38ea3f2cd88ceca8e0927d53e9770598bc",
"production": "docker",
"fuelmain_sha": "6b05280621c23ab158e9943f88b6f71a22fd4c69",
"astute_sha": "99a790ad1b7526cbbd5bf8add0cb2b4e503fccd4",
"feature_groups": ["mirantis"],
"release": "5.1",
"fuellib_sha": "25eb632c70fe0bb3b2c1053314b558a160e4af50"

1. Create new environment (Ubuntu, HA mode)
2. Choose GRE segmentation
3. Add 3 controllers+cinder, 1 compute
4. Start deployment. It has failed on second controller (node-2)
5. There is error in puppet.log:

2014-08-05 15:46:51 ERR

 (/Stage[main]/Rabbitmq::Service/Service[p_rabbitmq-server]) Provider pacemaker is not functional on this host

And there is message in /var/log/pacemaker.log:

<27>Aug 5 14:44:51 node-2 corosync[14380]: [SERV ] Service failed to load 'pacemaker'.

[Bogdan Dobrelya (bogdando)]

There are multiple "no server suitable for synchronization found" in logs, likely pacemaker cluster was affected by time desync issue

[Bogdan Dobrelya (bogdando)]

related https://bugs.launchpad.net/fuel/+bug/1314958 ntpd issue should be addressed in order to fix this one as well