Comment 1 for bug 1628653

So I definitely think we should tweak this. I had at least one upgrade job failing because of failed resources:
Failed Actions:
* memcached_monitor_60000 on overcloud-controller-1 'not running' (7): call=41, status=complete, exitreason='none', last-rc-change='Wed Sep 28 18:58:44 2016', queued=0ms, exec=0ms
* mongod_monitor_60000 on overcloud-controller-1 'not running' (7): call=82, status=complete, exitreason='none',last-rc-change='Wed Sep 28 18:58:06 2016', queued=0ms, exec=0ms
....

But we actually had all the resources running:
[root@overcloud-controller-0 ~]# pcs status |grep -i stopped
[root@overcloud-controller-0 ~]#