[Pacemaker] How to find out why pacemaker skipped action?

[Andrew Beekhof]

> On 27 Oct 2014, at 10:30 pm, Andrei Borzenkov <arvidjaar at gmail.com> wrote:
> 
> On Mon, Oct 27, 2014 at 12:40 PM, Andrew Beekhof <andrew at beekhof.net> wrote:
>> 
>>> On 27 Oct 2014, at 7:36 pm, Andrei Borzenkov <arvidjaar at gmail.com> wrote:
>>> 
>>> On Wed, Oct 22, 2014 at 8:59 AM, Andrew Beekhof <andrew at beekhof.net> wrote:
>>>> 
>>>>> On 22 Oct 2014, at 4:34 pm, Andrei Borzenkov <arvidjaar at gmail.com> wrote:
>>>>> 
>>>>> On Wed, Oct 22, 2014 at 8:01 AM, Andrew Beekhof <andrew at beekhof.net> wrote:
>>>>>> 
>>>>>>> On 21 Oct 2014, at 11:15 pm, Andrei Borzenkov <arvidjaar at gmail.com> wrote:
>>>>>>> 
>>>>>>> Pacemaker 1.1.11. I see in engine logs that it is going to restart resource:
>>>>>>> 
>>>>>>> Oct 21 12:34:50 n2 pengine[19748]:   notice: LogActions: Restart
>>>>>>> rsc_SAPHana_HDB_HDB00:0 (Master n2)
>>>>>>> 
>>>>>>> But I never see actual stop/start action being executed and in summary I get
>>>>>>> 
>>>>>>> Oct 21 12:35:11 n2 crmd[19749]:   notice: run_graph: Transition 32
>>>>>>> (Complete=10, Pending=0, Fired=0, Skipped=13, Incomplete=3,
>>>>>>> Source=/var/lib/pacemaker/pengine/pe-input-31.bz2): Stopped
>>>>>>> 
>>>>>>> So 13 actions were skipped and I presume restart was among them.
>>>>>>> 
>>>>>>> In which logs can I find explanation why actions were skipped? I do
>>>>>>> not see anything obvious.
>>>>>> 
>>>>>> Do you see any actions failing?
>>>>> 
>>>>> Yes
>>>>> 
>>>>> Oct 21 12:35:10 n2 crmd[19749]:  warning: status_from_rc: Action 11
>>>>> (rsc_SAPHanaTopology_HDB_HDB00:1_monitor_0) on n1 failed (target: 7
>>>>> vs. rc: 0): Error
>>>>> Oct 21 12:35:10 n2 crmd[19749]:  warning: status_from_rc: Action 11
>>>>> (rsc_SAPHanaTopology_HDB_HDB00:1_monitor_0) on n1 failed (target: 7
>>>>> vs. rc: 0): Error
>>>>> 
>>>>> Now there is the following ordering:
>>>>> 
>>>>> order ord_SAPHana_HDB_HDB00 2000: cln_SAPHanaTopology_HDB_HDB00
>>>>> msl_SAPHana_HDB_HDB00
>>>>> 
>>>>>> Further up the crmd should have said why the transaction is being aborted
>>>>>> 
>>>>> 
>>>>> If it says it, I do not yet understand it.
>>>>> 
>>>>> Am I right that if any action during transaction returns unexpected
>>>>> result, transaction is aborted?
>>>> 
>>>> Yes, and a new one calculated
>>> 
>>> Do CIB updates also abort running transaction?
>> 
>> Unexpected ones do, yes.
>> 
> 
> OK, monitoring script does "crm_attribute -N $(uname -n) -n foo -v
> bar". Is it expected?

Pacemaker has no idea the agent will run that, so no.
However, if 'foo' is already set to 'bar', then there is no change and the transition will not be interrupted

> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org