On 22/08/2013, at 10:22 PM, Ferenc Wagner <[email protected]> wrote:

> Hi,
> 
> man cibadmin says: "the tagname and all attributes must match in order
> for the element to be deleted",

"for the element to be deleted" <--- not the children of the element to be 
deleted

> but experience says otherwise: the
> primitive is deleted even if it was created with different attributes
> than those provided to the --delete call, cf. 'foo' vs 'bar' in the
> example below.  Do I misinterpret the documentation or is this a bug in
> Pacemaker 1.1.7?
> 
> # cibadmin --create --obj_type resources --xml-text "<primitive class='ocf' 
> provider='heartbeat' type='Dummy' id='test_dummy'>
>  <instance_attributes id='test_dummy-instance_attributes'>
>    <nvpair id='test_dummy-instance_attributes-fake' name='fake' value='foo'/>
>  </instance_attributes>
>  <meta_attributes id='test_dummy-meta_attributes'>
>    <nvpair id='test-dummy-meta_attributes-is-managed' name='is-managed' 
> value='false'/>
>  </meta_attributes>"
> 
> # cibadmin --delete --obj_type resources --xml-text "<primitive class='ocf' 
> provider='heartbeat' type='Dummy' id='test_dummy'>

tagname, class, provider, type and id all match here. so deletion is allowed to 
proceed

>  <instance_attributes id='test_dummy-instance_attributes'>
>    <nvpair id='test_dummy-instance_attributes-fake' name='fake' value='bar'/>
>  </instance_attributes>
>  <meta_attributes id='test_dummy-meta_attributes'>
>    <nvpair id='test-dummy-meta_attributes-is-managed' name='is-managed' 
> value='false'/>
>  </meta_attributes>"
> -- 
> Thanks,
> Feri.
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to