Probably best to clone it instead - so that we don't forget to update pcs once its implemented in pacemaker

Created attachment 1039999 [details]
proposed fix

Test:

[root@rh71-node1:~]# pcs resource create dummy dummy
[root@rh71-node1:~]# pcs resource create state stateful --master
Warning: changing a monitor operation interval from 10 to 11 to make the operation unique
[root@rh71-node1:~]# pcs resource debug-promote state
Operation promote for state:0 (ocf:pacemaker:Stateful) returned 0
[root@rh71-node1:~]# echo $?
0
[root@rh71-node1:~]# pcs resource debug-demote state
Operation demote for state:0 (ocf:pacemaker:Stateful) returned 0
[root@rh71-node1:~]# echo $?
0
[root@rh71-node1:~]# pcs resource debug-promote dummy
Error performing operation: No such process
Operation promote for dummy (ocf:heartbeat:Dummy) returned 3
 >  stdout: usage: /usr/lib/ocf/resource.d/heartbeat/Dummy {start|stop|monitor|migrate_to|migrate_from|validate-all|meta-data}
 >  stdout: 
 >  stdout: Expects to have a fully populated OCF RA-compliant environment set.
[root@rh71-node1:~]# echo $?
3
[root@rh71-node1:~]# pcs resource debug-demote dummy
Error performing operation: No such process
Operation demote for dummy (ocf:heartbeat:Dummy) returned 3
 >  stdout: usage: /usr/lib/ocf/resource.d/heartbeat/Dummy {start|stop|monitor|migrate_to|migrate_from|validate-all|meta-data}
 >  stdout: 
 >  stdout: Expects to have a fully populated OCF RA-compliant environment set.
[root@rh71-node1:~]# echo $?
3

Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.140-1.el7.x86_64
[root@rh71-node1:~]# pcs resource create dummy dummy
[root@rh71-node1:~]# pcs resource create state stateful --master
Warning: changing a monitor operation interval from 10 to 11 to make the operation unique
[root@rh71-node1:~]# pcs resource debug-promote state

Usage: pcs resource [commands]...
{snip}
[root@rh71-node1:~]# pcs resource debug-demote state

Usage: pcs resource [commands]...
{snip}



After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.141-1.el7.x86_64
See the previous comment bz1185096#c5

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-2290.html