Created attachment 958611 [details]
crm report

Scenario.
I have openstack HA deployed by staypuft.
I stopped neutron-l3-agent on one of the controllers by running systemctl stop neutron-l3-agent.Usually,after a few seconds,pacemaker starts the service again.
I tried to create a scenario where pacemaker fails to start the service and starts it on another available cluster node, so I stopped the service and  renamed the neutron-l3-agent executable file. Pacemaker was unable to start the service but it didn't start it on another node.

Here is systemctl status:
-----------------------------------------------------------------------------
root@mac848f69fbc4c3 bin]# systemctl status neutron-l3-agent
neutron-l3-agent.service - OpenStack Neutron Layer 3 Agent
   Loaded: loaded (/usr/lib/systemd/system/neutron-l3-agent.service; disabled)
   Active: failed (Result: exit-code) since Tue 2014-11-18 15:30:11 IST; 11min ago
 Main PID: 60553 (code=exited, status=203/EXEC)

Nov 18 15:30:11 mac848f69fbc4c3.example.com systemd[1]: Started OpenStack Neutron Layer 3 Agent.
Nov 18 15:30:11 mac848f69fbc4c3.example.com systemd[60553]: Failed at step EXEC spawning /usr/bin/neutron-l3-agent: No such file or directory
Nov 18 15:30:11 mac848f69fbc4c3.example.com systemd[1]: neutron-l3-agent.service: main process exited, code=exited, status=203/EXEC
Nov 18 15:30:11 mac848f69fbc4c3.example.com systemd[1]: Unit neutron-l3-agent.service entered failed state.
Nov 18 15:30:13 mac848f69fbc4c3.example.com systemd[1]: Stopped OpenStack Neutron Layer 3 Agent.
-----------------------------------------------------------------------------

You can find pcs status output here - http://pastebin.test.redhat.com/247106
You can find pcs config output here - http://pastebin.test.redhat.com/247107
crm_report attached

pacemaker-cluster-libs-1.1.10-32.el7_0.1.x86_64
pacemaker-cli-1.1.10-32.el7_0.1.x86_64
pacemaker-libs-1.1.10-32.el7_0.1.x86_64
pacemaker-1.1.10-32.el7_0.1.x86_64