[Pacemaker] Call cib_apply_diff failed (-205): Update was older than existing configuration

Kostiantyn Ponomarenko konstantin.ponomarenko at gmail.com
Mon Feb 9 08:11:12 UTC 2015


Hi Kristoffer,

Thank you for the help.
I will let you know if I see the same with the latest version.
On Feb 9, 2015 10:07 AM, "Kristoffer Grönlund" <kgronlund at suse.com> wrote:

> Hi,
>
> Kostiantyn Ponomarenko <konstantin.ponomarenko at gmail.com> writes:
>
> > Hi guys,
> >
> > I saw this during applying the configuration using a script with crmsh
> > commands:
>
>
> The CIB patching performed by crmsh has been a bit too sensitive to
> CIB version mismatches which can cause errors like the one you are
> seeing. This should be fixed in the latest released version of crmsh
> (2.1.2), and I would recommend upgrading to that version if you can.
>
> If this problem still occurs with 2.1.2, please let me know [1].
>
> Thanks!
>
> [1]: http://github.com/crmsh/crmsh/issues
>
>
> >
> > + crm configure primitive STONITH_node-1 stonith:fence_avid_sbb_hw
> > + crm configure primitive STONITH_node-0 stonith:fence_avid_sbb_hw params
> > delay=10
> > + crm configure location dont_run_STONITH_node-1_on_node-1 STONITH_node-1
> > -inf: node-1
> > + crm configure location dont_run_STONITH_node-0_on_node-0 STONITH_node-0
> > -inf: node-0
> > Call cib_apply_diff failed (-205): Update was older than existing
> > configuration
> > ERROR: could not patch cib (rc=205)
> > INFO: offending xml diff: <diff format="2">
> >   <version>
> >     <source admin_epoch="0" epoch="26" num_updates="3"/>
> >     <target admin_epoch="0" epoch="27" num_updates="3"/>
> >   </version>
> >   <change operation="modify" path="/cib">
> >     <change-list>
> >       <change-attr name="epoch" operation="set" value="27"/>
> >     </change-list>
> >     <change-result>
> >       <cib crm_feature_set="3.0.9" validate-with="pacemaker-2.0"
> epoch="27"
> > num_updates="3" admin_epoch="0" cib-last-written="Thu Feb  5 14:56:09
> 2015"
> > have-quorum="1" dc-uuid="1"/>
> >     </change-result>
> >   </change>
> >   <change operation="create" path="/cib/configuration/constraints"
> > position="1">
> >     <rsc_location id="dont_run_STONITH_node-0_on_node-0"
> > rsc="STONITH_node-0" score="-INFINITY" node="node-0"/>
> >   </change>
> > </diff>
> >
> > After that pacemaker stopped on the node on which the script was run.
> >
> > Thank you,
> > Kostya
> > _______________________________________________
> > 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
>
> --
> // Kristoffer Grönlund
> // kgronlund at suse.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20150209/c1030cb5/attachment.htm>


More information about the Pacemaker mailing list