[Linux-HA] crm_attribute and cib-bootstrap-options

[Andreas Kurz]

Hello!

I was doing some maintenance on a live cluster and tried
"crm_attribute -t crm_config -n is_managed_default -v false" instead of
using cibadmin.

I noticed, that it was not working because crm_attribute assumes that
the id of the "is_managed_default attribute" is
"cib-bootstrap-options-is_managed_default". So after executing it, the
crm-config looks like this:

<crm_config>
   <cluster_property_set id="cib-bootstrap-options">
     <attributes>
       <nvpair name="default_action_timeout" id="default_action_timout"
value="60s"/>
       <nvpair name="default_resource_failure_stickiness"
id="default_resource_failure_stickiness" value="0"/>
       <nvpair name="default_resource_stickiness"
id="default_resource_stickiness" value="100"/>
       <nvpair id="is_managed_default" name="is_managed_default"
value="true"/>
       <nvpair id="no_quorum_policy" name="no_quorum_policy"
value="ignore"/>
       <nvpair id="require_quorum" name="require_quorum" value="true"/>
       <nvpair id="remove_after_stop" name="remove_after_stop"
value="true"/>
       <nvpair id="short_resource_names" name="short_resource_names"
value="true"/>
       <nvpair id="stop_orphan_actions" name="stop_orphan_actions"
value="true"/>
       <nvpair id="stop_orphan_resources" name="stop_orphan_resources"
value="true"/>
       <nvpair id="suppress_cib_writes" name="suppress_cib_writes"
value="false"/>
       <nvpair id="symmetric_cluster" name="symmetric_cluster"
value="true"/>
       <nvpair id="transition_idle_timeout" name="transition_timeout"
value="60s"/>
       <nvpair id="transition_timeout" name="transition_timeout"
value="60s"/>
       <nvpair id="stonith_action" name="stonith_action" value="reboot"/>
       <nvpair id="stonith_enabled" name="stonith_enabled" value="true"/>
       <nvpair id="cib-bootstrap-options-last-lrm-refresh"
name="last-lrm-refresh" value="1165846863"/>
       <nvpair id="cib-bootstrap-options-is_managed_default"
name="is_managed_default" value="false"/>
     </attributes>
   </cluster_property_set>
 </crm_config>

And the resources were still managed.

Is this a bug in crm_attribute or is there a not enforced rule, that
also the ids in this special cluster_property_set have to start with
cib-bootstrap-options?

Regards,
Andi