[Pacemaker] What is the reason which the node in which failure has not occurred carries out "lost"?

[Yusuke Iida]

Hi, Andrew

crm_mon has the processing which makes cib the newest, when
pcmk_err_old_data is still received.

Since this processing can be considered to be unnecessary like the
processing changed by stonithd, I correct this.

Please merge the following, if satisfactory.
https://github.com/ClusterLabs/pacemaker/pull/477

Regards,
Yusuke

2014-03-18 9:56 GMT+09:00 Andrew Beekhof <andrew at beekhof.net>:
>
> On 12 Mar 2014, at 1:45 pm, Yusuke Iida <yusk.iida at gmail.com> wrote:
>
>> Hi, Andrew
>> 2014-03-12 6:37 GMT+09:00 Andrew Beekhof <andrew at beekhof.net>:
>>>> Mar 07 13:24:14 [2528] vm01       crmd: (te_callbacks:493   )   error:
>>>> te_update_diff: Ingoring create operation for /cib 0xf91c10,
>>>> configuration
>>>
>>> Thats interesting... is that with the fixes mentioned above?
>> I'm sorry.
>> The above-mentioned log is not outputted by the newest Pacemaker.
>> The following logs come out in the newest thing.
>>
>> Mar 12 10:43:38 [6124] vm02       crmd: (te_callbacks:377   )   trace:
>> te_update_diff:  Handling create operation for /cib/configuration
>> 0x1c37c60, fencing-topology
>> Mar 12 10:43:38 [6124] vm02       crmd: (te_callbacks:493   )   error:
>> te_update_diff:  Ingoring create operation for /cib/configuration
>> 0x1c37c60, fencing-topology
>> Mar 12 10:43:38 [6124] vm02       crmd: (te_callbacks:377   )   trace:
>> te_update_diff:  Handling create operation for /cib/configuration
>> 0x1c397a0, rsc_defaults
>> Mar 12 10:43:38 [6124] vm02       crmd: (te_callbacks:493   )   error:
>> te_update_diff:  Ingoring create operation for /cib/configuration
>> 0x1c397a0, rsc_defaults
>>
>> I checked code of te_update_diff.
>> Should not the next judgment be changed if change of fencing-topology
>> or rsc_defaults is processed as a configuration subordinate's change?
>
> Perfect!
>
>   https://github.com/beekhof/pacemaker/commit/1c285ac
>
> Thanks to everyone for giving the new CIB a pounding, we should be in very good shape for a release soon :-)
>
>>
>> diff --git a/crmd/te_callbacks.c b/crmd/te_callbacks.c
>> index dd57660..f97bab5 100644
>> --- a/crmd/te_callbacks.c
>> +++ b/crmd/te_callbacks.c
>> @@ -378,7 +378,7 @@ te_update_diff(const char *event, xmlNode * msg)
>>         if(xpath == NULL) {
>>             /* Version field, ignore */
>>
>> -        } else if(strstr(xpath, "/cib/configuration/")) {
>> +        } else if(strstr(xpath, "/cib/configuration")) {
>>             abort_transition(INFINITY, tg_restart, "Non-status
>> change", change);
>>
>>         } else if(strstr(xpath, "/"XML_CIB_TAG_TICKETS"[") ||
>> safe_str_eq(name, XML_CIB_TAG_TICKETS)) {
>>
>> How is such change?
>>
>> I attach report at this time.
>> The trace log of te_update_diff is also contained.
>> https://drive.google.com/file/d/0BwMFJItoO-fVeVVEemVsZVBoUWc/edit?usp=sharing
>>
>> Regards,
>> Yusuke
>>>
>>>>
>>>>>
>>>>>> but it looks like crmsh is doing something funny with its updates... does anyone know what command it is running?
>>>>
>>>> The execution result of the following commands remained in /var/log/messages.
>>>>
>>>> Mar  7 13:24:14 vm01 cibadmin[2555]:   notice: crm_log_args: Invoked:
>>>> cibadmin -p -R --force
>>>
>>> I'm somewhat confused at this point.... if crmsh is using --replace, then why is it doing diff calculations?
>>> Or are replace operations only for the load operation?
>>
>>
>>
>>
>> --
>> ----------------------------------------
>> METRO SYSTEMS CO., LTD
>>
>> Yusuke Iida
>> Mail: yusk.iida at gmail.com
>> ----------------------------------------
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> 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
>



-- 
----------------------------------------
METRO SYSTEMS CO., LTD

Yusuke Iida
Mail: yusk.iida at gmail.com
----------------------------------------