Pacemaker failed actions following OpenStack deployment
Issue
- Running 'pcs status' reveals failed actions at the bottom of the output:
Failed Actions:
* openstack-heat-engine_start_0 on overcloud-controller-1 'not running' (7): call=141, status=complete, exitreason='none',
last-rc-change='Sun Feb 28 06:29:50 2016', queued=0ms, exec=2141ms
* openstack-heat-engine_start_0 on overcloud-controller-0 'not running' (7): call=142, status=complete, exitreason='none',
last-rc-change='Sun Feb 28 06:28:36 2016', queued=0ms, exec=2151ms
* openstack-heat-engine_start_0 on overcloud-controller-2 'not running' (7): call=140, status=complete, exitreason='none',
last-rc-change='Sun Feb 28 06:29:31 2016', queued=0ms, exec=2139ms
Environment
- Red Hat OpenStack Platform
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.