[ClusterLabs] Finding attributes of a past resource agent invocation

[wferi at niif.hu]

Hi,

I suffered unexpected fencing under Pacemaker 2.0.1.  I set a resource
to unmanaged (crm_resource -r vm-invtest -m -p is-managed -v false),
then played with ocf-tester, which left the resource stopped.  Finally I
deleted the resource (crm_resource -r vm-invtest --delete -t primitive),
which led to:

pacemaker-controld[11670]:  notice: State transition S_IDLE -> S_POLICY_ENGINE 
pacemaker-schedulerd[11669]:  notice: Clearing failure of vm-invtest on inv1 because resource parameters have changed 
pacemaker-schedulerd[11669]:  warning: Processing failed monitor of vm-invtest on inv1: not running 
pacemaker-schedulerd[11669]:  warning: Detected active orphan vm-invtest running on inv1
pacemaker-schedulerd[11669]:  notice: Clearing failure of vm-invtest on inv1 because it is orphaned 
pacemaker-schedulerd[11669]:  notice:  * Stop       vm-invtest       (  inv1 )   due to node availability
pacemaker-schedulerd[11669]:  notice: Calculated transition 959, saving inputs in /var/lib/pacemaker/pengine/pe-input-87.bz2
pacemaker-controld[11670]:  notice: Initiating stop operation vm-invtest_stop_0 on inv1 
pacemaker-controld[11670]:  notice: Transition 959 aborted by deletion of lrm_rsc_op[@id='vm-invtest_last_failure_0']: Resource operation removal 
pacemaker-controld[11670]:  warning: Action 6 (vm-invtest_stop_0) on inv1 failed (target: 0 vs. rc: 6): Error
pacemaker-controld[11670]:  notice: Transition 959 (Complete=5, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-87.bz2): Complete
pacemaker-schedulerd[11669]:  warning: Processing failed stop of vm-invtest on inv1: not configured 
pacemaker-schedulerd[11669]:  error: Preventing vm-invtest from re-starting anywhere: operation stop failed 'not configured' (6)
pacemaker-schedulerd[11669]:  warning: Processing failed stop of vm-invtest on inv1: not configured 
pacemaker-schedulerd[11669]:  error: Preventing vm-invtest from re-starting anywhere: operation stop failed 'not configured' (6)
pacemaker-schedulerd[11669]:  warning: Cluster node inv1 will be fenced: vm-invtest failed there
pacemaker-schedulerd[11669]:  warning: Detected active orphan vm-invtest running on inv1
pacemaker-schedulerd[11669]:  warning: Scheduling Node inv1 for STONITH
pacemaker-schedulerd[11669]:  notice: Stop of failed resource vm-invtest is implicit after inv1 is fenced
pacemaker-schedulerd[11669]:  notice:  * Fence (reboot) inv1 'vm-invtest failed there'
pacemaker-schedulerd[11669]:  notice:  * Move       fencing-inv3     ( inv1 -> inv2 )  
pacemaker-schedulerd[11669]:  notice:  * Stop       vm-invtest       (         inv1 )   due to node availability

The OCF resource agent (on inv1) reported that it failed to validate one
of the attributes passed to it for the stop operation, hence the "not
configured" error, which caused the fencing.  Is there a way to find out
what attributes were passed to the OCF agent in that fateful invocation?
I've got pe-input files, Pacemaker detail logs and a hard time wading
through them.  I failed to reproduce the issue till now (but I haven't
rewound the CIB yet).
-- 
Thanks,
Feri